I have got a NetBSD build of the bootloader to come up with a prompt
and respond to typed commands. The trick was to just let the data
section follow on after text. The a.out version of objcopy seems to
get confused if there is a gap between text and data.
I have added CONFIG_ASSABET as a build option and ASSABET_ARCH as an
architecture type.
The two things that don't work are XMODEM downloads and identifying
the flash device. I expect that the XMODEM problem is just some silly
mistake of mine, the flash problem is more complicated.
The calls to queryFlashID in btflash_init return garbage values for
mftid and devid.
I get the same error if I put bootldr-0000-2.8.4 into flash on my board,
so I don't think it is a build problem.
The only thing that a collegue and I can think of is that the bus cycles
needed to fetch instructions are causing the flash to drop out of read
identifier codes mode before the vendor and device ids can be read.
I'll generate some diffs tomorrow anyway so that you can check they
will still work for Linux builds.
Robert
Received on Wed Aug 9 15:14:02 2000
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:46:07 EDT