201 lines · 6.2 KB · Text
RawDownload
beagleboard rev c3:cortex-a8 cpu: arm v7-a arch. rev 3, 500MHz, dual-issueOMAP3530-GP rev 2, CPU-OPP2 L3-165MHzOMAP3 Beagle board + LPDDR/NANDDRAM:  256 MBNAND:  256 MiBBoard revision CSerial #784200230000000004013f790401d018 igepv2 board:cortex-a8 cpu: arm v7-a arch. rev 3, 720MHz, dual-issueOMAP3530-GP ES3.1, CPU-OPP2 L3-165MHzIGEP v2.x rev. B + LPDDR/ONENANDDRAM:  512 MBMuxed OneNAND(DDP) 512MB 1.8V 16-bit (0x58)OneNAND version = 0x0031Chip support all block unlockChip has 2 planeScanning device for bad blocksBad eraseblock 3134 at 0x187c0000Bad eraseblock 3135 at 0x187e0000OneNAND: 512 MB omap3530 SoCCORE_CLK runs at 26MHzsee spruf98d from ti.com (/public/doc/ti/omap35x.ref.spruf98d.pdf) separate i & d tlbs, each 32 entries	can invalidate i, d or both tlbs by { all, mva, or asid match } i & d L1 caches, 16K each, 4 ways, 64 sets, 64-byte lines	i is VIPT, d is PIPT	no `test and clean D & U all' operations	no prefetching, no cache maintenance	can invalidate i, d or both cache but not D & U all	can invalidate entire i-cache only	can clean or invalidate by set and way data/unified cacheunified L2 PIPT cache, 256K, 8 ways, 512 sets, 64-byte linesno hardware cache coherence l3 interconnect firewalls are all off at boot time, except for a bit of	secure ramsram at 0x40200000 size 1MBl4 interconnect firewalls seem to be sane at boot time ___The state of the Beagleboard/IGEPv2 (TI OMAP35 SoC, Cortex-A8) port. Plan 9 runs on the IGEPv2 and Gumstix Overo boards. On the Beagleboard, Plan 9 is not yet usable but it gets as far astrying to access the USB ethernet (since the Beagleboard has nobuilt-in ethernet and must use USB ethernet). IGEP & Gumstix Ethernet The smsc9221 ethernet consumes a lot of system time.  The designdecision to use fifos rather than buffer rings and to not incorporatedma into the ethernet controller is probably responsible.  With only asingle core, running the 9221 consumes a lot of the available CPUtime.  It's probably worth trying to use the system dma controller again. USB The ohci and ehci controllers are seen, but no devices yet. There are four USB errata that need to be looked into for the igepv2(silicon 3.1) at least.  From the omap3530 errata (rev e): - 3.1.1.130 only one usb dma channel (rx or tx) can be active	at one time: use interrupt mode instead- 3.1.1.144 otg soft reset doesn't work right- 3.1.1.183 ohci and ehci controllers cannot work concurrently- §3.1.3 usb limitations: all ports must be configured to identical speeds	(high vs full/low) Flash access to nand flash would be handy for nvram and paqfs file systems. In the flash, x-loader occupies up to 0x20000, then u-boot from0x80000 to 0x1e0000, and there's a linux kernel after that (if youcare).  The beagle's flash chip is a micron pop 2Gb nandmt29f2g16abdhc-et (physical marking jw256), and the igep's is asamsung onenand. VFPv3 Floating Point The Cortex-A8 has VFPv3 floating point, which uses different opcodesthan 5c/5l currently generate.  New 5c or 5l is in the works. Video The display subsystem for omap3 (dss) is divided into 3 parts, called lcd,video and dsi (ignoring the various accelerators).  The system onlysupports the lcd via dvi interface so far because it's the only one wehave been able to test.  1280x1024x16 is the default resolution, thismight be changed.  Writing to /dev/dssctl (e.g., echo 1024x768x16>/dev/dssctl) changes the resolution.  Currently the system does notuse the rfbi since it seems like an unnecessary optimisation at thispoint.  Per Odlund wrote the first draft of the video driver for aGoogle Summer of Code project. Stray Interrupts IRQs 56 and 57 are I2C.  83, 86 and 94 are MMC. ___ The code is fairly heavy-handed with the use of barrier instructions(BARRIERS in assembler, coherence in C), partly in reaction to badexperience doing Power PC ports, but also just as precautions againstmodern processors, which may feel free to execute instructions out oforder or some time later, store to memory out of order or some timelater, otherwise break the model of traditional sequential processors,or any combination of the above.___ There are a few rough edges: - the clock.c scheduling rate (HZ) is quite approximate.  The OMAPtimers are complex, but one could eventually do better (or just lettimesync compensate). - User processes are limited to 512MB virtual (mainly by the IGEPv2 Ethernetbeing at 0x2c000000), which isn't a problem since Beagleboards onlyhave 256MB of dram and IGEPv2s have 512MB, and we don't want to swap. - might use ucalloc.c to allocate uncached scratch space for generated codein coproc.c. - the C implementation of cache primitives failed with mmu off; still true? - unlock, setup: protect module register target APE (PM_RT) per spruf98c §1.6.7 - setup mpp (multi-purpose pins)? ___	memory map (mostly from omap35x ref)hex addr	size	what----0		16MB	physical address of flash registers, buffers20000000	16MB	virtual address of flash registers, buffers2c000000	?	smc 9221 ethernet38000000	16MB	256MB (beagle) or 512MB (igep) nand flash mapped here 40000000	112K	boot rom, top of user space40200000	64K	sram 48000000	16MB	L4 core48002000	8K	system control (scm)48004000	16K	clock manager48040000	8K	L4-core config48050000	4K	graphics48062000	4K	usb tll48064000	1K	usb uhh_config48064400	1K	ohci48064800	1K	ehci4806a000	8K	8250 uart04806c000	8K	8250 uart148086000	4K	gptimer1048088000	4K	gptimer114809c000	8K	mmc/sd goo480ab000	8K	hs usb otg480ad000	8K	mmc/sd goo480b4000	8K	mmc/sd goo480c7000		device intr controller48200000	2K	intr ctlr (intc) 48300000	256K	L4-wakeup48304000	4K	gptimer1248318000	8K	gptimer1 49000000	1MB	L4 peripherals49020000	8K	8250 uart2 (with exposed connector for console)49032000	4K	gptimer249034000	4K	gptimer3⋯49040000	4K	gptimer949050000	8K	gpio2⋯49058000	8K	gpio6 50000000	64K	graphics accelerator 68000000	1K	L3 config (rt)68004000	1K	L3 hs usb host68004400	1K	L3 hs usb otg68005400	1K	L3 graphics68006800	1K	L4-core config68010000		L3 protection mechanism 6e000000	?	gpmc 80000000	256MB	dram on beagle		512MB	dram on igep c0000000	1GB	kernel virtual space, mapped to 80000000 apparently the vector address (0 or 0xffff0000) is virtual,so we're expected to map it to ram.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t