Dear Chuck,
In message 002b01cea8e7$b14fc5b0$13ef5110$@amanomcgann.com you wrote:
I found if I used tftp these files transferred correctly and the board would boot with the new files. I thought the solution was found and I could simply setup the same files using USB through environment variables. The script worked but the problem was when it tried to load rootfs into RAM it would cause a CPU reset and RomBOOT to start. At first I thought there was something wrong with the script so I tried to load the file by typing it the command but got the same result.
Are you using the same load address in RAM with both the tftp and the fatload commands? Can you provide a complete console log of both the working and the crashing cases?
Command:
usb start
fatload usb 0 $(loadaddr) rootfs.ext2.gz.uboot where loadaddr is the same address used by tftp.
Please show the complete commands, and all output.
My first question is, is there a solution for this issue using U-Boot 2009.11.1? This version builds currently within our project.
We need to understand the problem beforeanybody could answer that...
Second question is I downloaded U-Boot 2013.07 but noticed huge change in the build process. I figured out the patches I need along with the AT91 configuration for our board. We are using the arm926ej6 processor with a board similar to at91sam9260ek. When I try to build I get the hardware.h:49:3 error: #error "Unsupported AT91 processor" message. When I look at the header file I see where it fails but I don't understand why since I do have a matching define. For some reason hardware.h is not seeing this define and I am stumped as to why. So any suggestions on how to solve or figure this out would be appreciated.
Well, 2009.11 is indeed extremely old. With such an out-of-tree port you are essentially lost. Adapting the old patches to current mainline is more or less the same effort as starting from scratch (and probably even more so).
Best regards,
Wolfgang Denk