| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
8k boundary with this program still.
text data bss dec hex filename
7925 4 4476 12405 3075 bootiic.out
so we have like 293 bytes left before we have to play games. There
may be ways to reduce that somewhat, but they start to be very board
specific.
|
|
|
|
|
|
| |
Reach over into the arm tree to grab some at91 definitions.
Better warnings
Lots of build tweaks
|
| |
|
|
|
|
|
| |
Remove obsolete files in list
Add spi flash reading routines
|
|
|
|
|
| |
reduce code footprint, etc. While some problems still remain, the
reliability of tftp is much improved.
|
| |
|
|
|
|
| |
are too hard to share between the different boot loaders.
|
|
|
|
| |
really an offset within the eeprom device, and not a IIC address.
|
| |
|
| |
|
|
|
|
|
|
|
| |
changes in the future. This helps with getting started and to
overcome the really sucky level of granuality this timeout has in
getc. A timeout of 1 means 'wait until top of next second' rather
than 'wait for at least a second'.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This change affects documentation and comments only,
no real code involved.
PR: misc/101245
Submitted by: Darren Pilgrim <darren pilgrim bitfreak org>
Tested by: md5(1)
MFC after: 1 week
|
| |
|
|
|
|
|
| |
While I'm here remove a stale wx(4) entry which was removed 4 years,
9 months ago.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
fixes filesystem corruption when nextboot.conf is located after
cylinder 1023. The bug appears to have been introduced at the time
bd_read was copied to create bd_write.
PR: bin/98005
Reported by: yar
MFC after: 1 week
|
|
|
|
|
|
| |
entry for the replacement le(4) module.
- Add an entry for the gem(4) module.
- Remove gratuitous whitespace in the description of the hme(4) entry.
|
| |
|
|
|
|
| |
stale comments.
|
| |
|
| |
|
|
|
|
| |
Pointyhat to: nyan
|
|
|
|
|
|
|
|
|
|
|
| |
selection and not always beeping on startup. The two bytes for the extra
'jmp' instruction were obtained by removing recognition of BSD/OS
partitions.
Requested by: many
Tested by: subset of many
Head nod: imp, keramida
MFC after: 2 weeks
|
|
|
|
|
| |
in the loader when searching for the ACPI RSDP. (The loader runs in a flat
mode with va 0 == pa 0xa000.)
|
|
|
|
|
| |
Make getc(0) polling (this has the happy side effect of saving
8 bytes in the generated code).
|
| |
|
| |
|
|
|
|
|
|
| |
Init eeprom here now that we don't init the eeprom in arm_init.s
and read in the second 8k of the data.
Tweak formatting.
|
|
|
|
|
| |
boot loader (linux booting helps regression testing). No repo copy
because of limited history.
|
| |
|
| |
|
|
|
|
|
| |
On the KB9202 go ahead and enable the flash controller so the boot
loader can access the parallel flash.
|
|
|
|
|
|
|
| |
Make this compile, assuming that you have linux installed in a
sensible place. tag_list is disabled by default, since we don't
distribute linux, but it is desirable to allow the boot loader to boot
Linux or FreeBSD (mostly for testing).
|
|
|
|
| |
Minor diffs to reduce diffs to p4.
|
|
|
|
|
|
| |
xmodem download. Then download the image you want in the flash.
This will burn the image into the flash. You must then reset the
unit and the new flash image will be used for booting...
|
|
|
|
|
|
| |
xmodem download. Then download the image you want in the eeprom.
This will burn the image into the eeprom. You must then reset the
unit and the new eeprom image will be used for booting...
|
|
|
|
|
| |
to replace either a bad iic eeprom with one you download with xmodem,
or likewise with a spi flash.
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Use a directory layout that is more akin to the i386 boot layout.
o Create a libat91 for library routines that are used by one or more
of the boot loaders.
o Create bootiic for booting from an iic part.
o Create bootspi for booting from an spi part.
o Optimize the size of many of these routines (especially emac.c). Except
for the emac.c optimizations, all these have been tested.
o eliminate the inc directory, libat91 superceeds it.
o Move linker.cfg up a layer to allow it to be shared.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For 32-bit SDRAM systems, enable D16 to D31 in the PIO controller.
Otherwise they read back as 0xffff.
Shave 8 bytes from the object size by using AT91C_BASE_PIOA directly
and by not assigning PIO_BSR to 0 in the DBGU init. That's a nop in
two ways (everything defaults to peripheral A, and writing 0 changes
nothing).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Many places used #define FOO ((unsigned int) 0x23) where a simpler
#define FOO 0x23u would have sufficed. This practice is overly
verbose and has the disadvantage that you can't say
#if FOO == BAR
#endif
because the extra "unsigned int" tokens choke cpp's little brain.
Migrate to the latter style to allow use in preprocessor statements.
The two are the same semantically anyway in a C context (at least for
the uses they are put to presently, C gurus can explain to me how they
differ).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
via xmodem to the DBGU port when the AT91 comes up in recovery mode.
The recovery loader will then load your program via xmodem into SDRAM
at 1MB which can do its things. It needs to be tweaked to the
specific board one is using, but it fits in < 1kB (all of Atmel's ARM
products have at least 8kb of SRAM that I can tell, so this should
work for them all).
Parts of this code were provided by Kwikbyte with copyright
specifically disclaimed. I heavily modified it to act as a recovery
loader (before it was a bootstrap loader) and to optimize for size
(before I started the size was closer to 8k).
Bootstrap loaders for SPI and IIC to follow.
|
|
|
|
| |
MFC after: 1 day
|
|
|
|
|
| |
boot loaders that load the loader already handle A20. In fact, they are
required to do so in order to setup the environment that btxldr expects.
|
| |
|