arm/sa1100/assabet.rst

2 The Intel Assabet (SA-1110 evaluation) board
13 -------------------
25 -----------------------
27 A couple of bootloaders able to boot Linux on Assabet are available:
39    John Dorsey has produced add-on patches to add support for Assabet and
44    RedBoot is a bootloader developed by Red Hat based on the eCos RTOS
51 Brief examples on how to boot Linux with RedBoot are shown below.  But first
52 you need to have RedBoot installed in your flash memory.  A known to work
55 - ftp://ftp.netwinder.org/users/n/nico/
56 - ftp://ftp.arm.linux.org.uk/pub/linux/arm/people/nico/
57 - ftp://ftp.handhelds.org/pub/linux/arm/sa-1100-patches/
59 Look for redboot-assabet*.tgz.  Some installation infos are provided in
60 redboot-assabet*.txt.
64 -----------------------------
67 on-line at http://sources.redhat.com/ecos/docs.html.
70 If you have a CF network card (my Assabet kit contained a CF+ LP-E from
75 To initialize the flash directory::
77 	fis init -f
79 To initialize the non-volatile settings, like whether you want to use BOOTP or
82 	fconfig -i
85 Writing a kernel image into flash
86 ---------------------------------
89 available on a TFTP server::
91 	load zImage -r -b 0x100000
93 If you rather want to use Y-Modem upload over the serial port::
95 	load -m ymodem -r -b 0x100000
97 To write it to flash::
99 	fis create "Linux kernel" -b 0x100000 -l 0xc0000
103 ------------------
108 	load ramdisk_image.gz -r -b 0x800000
110 Again, Y-Modem upload can be used instead of TFTP by replacing the file name
111 by '-y ymodem'.
113 Now the kernel can be retrieved from flash like this::
119 	exec -b 0x100000 -l 0xc0000
121 The ramdisk image could be stored into flash as well, but there are better
122 solutions for on-flash filesystems as mentioned below.
126 -----------
128 Using JFFS2 (the Second Journalling Flash File System) is probably the most
129 convenient way to store a writable filesystem into flash.  JFFS2 is used in
130 conjunction with the MTD layer which is responsible for low-level flash
131 management.  More information on the Linux MTD can be found on-line at:
132 http://www.linux-mtd.infradead.org/.  A JFFS howto with some infos about
140 	load sample_img.jffs2 -r -b 0x100000
144 	RedBoot> load sample_img.jffs2 -r -b 0x100000
145 	Raw file loaded 0x00100000-0x00377424
147 Now we must know the size of the unallocated flash::
156 The values above may be different depending on the size of the filesystem and
157 the type of flash.  See their usage below as an example and take care of
162 	size of unallocated flash:	0x503c0000 - 0x500e0000 = 0x2e0000
163 	size of the filesystem image:	0x00377424 - 0x00100000 = 0x277424
166 the remaining flash space as well.  To write it::
168 	fis unlock -f 0x500E0000 -l 0x2e0000
169 	fis erase -f 0x500E0000 -l 0x2e0000
170 	fis write -b 0x100000 -l 0x277424 -f 0x500E0000
171 	fis create "JFFS2" -n -f 0x500E0000 -l 0x2e0000
178 	Name              FLASH addr  Mem addr    Length      Entry point
187 	SA1100 flash: probing 32-bit flash bus
188 	SA1100 flash: Found 2 x16 devices at 0x0 in 32-bit mode
190 	Creating 5 MTD partitions on "SA1100 flash":
191 	0x00000000-0x00020000 : "RedBoot"
192 	0x00020000-0x000e0000 : "Linux kernel"
193 	0x000e0000-0x003c0000 : "JFFS2"
194 	0x003c0000-0x003e0000 : "RedBoot config"
195 	0x003e0000-0x00400000 : "FIS directory"
199 Therefore to boot Linux with the kernel and its root filesystem in flash, we
203 	exec -b 0x100000 -l 0xc0000 -c "root=/dev/mtdblock2"
207 possible, and sometimes more convenient, to flash a filesystem directly from
209 many tools to deal with flash memory as well, to erase it for example.  JFFS2
210 can then be mounted directly on a freshly erased partition and files can be
215 -----------------
222 images retrieved from a TFTP server on the network::
228 	>> load zImage -r -b 0x100000
229 	>> load ramdisk_ks.gz -r -b 0x800000
230 	>> exec -b 0x100000 -l 0xc0000
236 	Update RedBoot non-volatile configuration - are you sure (y/n)? y
248 Status of peripherals in -rmk tree (updated 14/10/2001)
249 -------------------------------------------------------
254    - PM:		Not tested.
255    - COM:		TX, RX, CTS, DSR, DCD, RTS, DTR, PM
256    - PM:		Not tested.
257    - I2C:		Implemented, not fully tested.
258    - L3:		Fully tested, pass.
259    - PM:		Not tested.
262   - LCD:		Fully tested.  PM
266   - Video out:		Not fully
270   -  Playback:		Fully tested, pass.
271   -  Record:		Implemented, not tested.
272   -  PM:			Not tested.
275   -  Audio play:	Implemented, not heavily tested.
276   -  Audio rec:		Implemented, not heavily tested.
277   -  Telco audio play:	Implemented, not heavily tested.
278   -  Telco audio rec:	Implemented, not heavily tested.
279   -  POTS control:	No
280   -  Touchscreen:	Yes
281   -  PM:		Not tested.
284   - PCMCIA:
285   - LPE:		Fully tested, pass.
286   - USB:		No
287   - IRDA:
288   - SIR:		Fully tested, pass.
289   - FIR:		Fully tested, pass.
290   - PM:			Not tested.
294   - COM1,2:		TX, RX, CTS, DSR, DCD, RTS, DTR
295   - PM:			Not tested.
296   - USB:		Implemented, not heavily tested.
297   - PCMCIA:		Implemented, not heavily tested.
298   - CF:			Implemented, not heavily tested.
299   - PM:			Not tested.
301 More stuff can be found in the -np (Nicolas Pitre's) tree.