[U-Boot-Users] Maintainer of AT91RM9200DK???
Hi there,
who considers himself as the U-Boot maintainer of the AT91RM9200 cpu and the AT91RM9200DK eval board? Rick, is that you?
I just porting U-Boot to our AT91RM9200 based board and it migth be necessary to change some code in the AT91RM9200 relevant stuff. So I am looking for people to talk to before that.
Thanks a million.
Steven
Steven,
That would be me.
Rick
Hi there,
who considers himself as the U-Boot maintainer of the AT91RM9200 cpu and the AT91RM9200DK eval board? Rick, is that you?
I just porting U-Boot to our AT91RM9200 based board and it migth be necessary to change some code in the AT91RM9200 relevant stuff. So I am looking for people to talk to before that.
Thanks a million.
Steven
In message 3F913C5A.8070303@imc-berlin.de you wrote:
who considers himself as the U-Boot maintainer of the AT91RM9200 cpu and the AT91RM9200DK eval board? Rick, is that you?
Guess why he's listed in the MAINTAINERS file?
So I am looking for people to talk to before that.
There is always this mailing list.
Best regards,
Wolfgang Denk
hi all! We are porting u-boot to a no mmu board with cpu arm7tdmi. Now,all is ok when u-boot run in ram.But it seem have problem whem burned to flash!Some not regulation ascii code are printed to my terminal! Debug it and find no bug in it. Are there someone know this problem? thanks joe.2003.10.20
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
In message 20031020134915.50389.qmail@web41111.mail.yahoo.com you wrote:
We are porting u-boot to a no mmu board with cpuarm7tdmi. Now,all is ok when u-boot run in ram.But it seem
Obviously you have some external tool (JTAG debugger?) which is initializing your RAM so that you can use it to load and run U-Boot.
have problem whem burned to flash!Some not regulation ascii code are printed to my terminal! Debug it and find no bug in it. Are there someone know this problem?
When run from flash, probably your RAM initialization is instead performed by U-Boot. Probably there is some problem in that area...
Best regards,
Wolfgang Denk
WD and all: At first,Thanks the WD that help me to solve the last problem! the other problem is why I set the #define CFG_ENV_ADDR (PHYS_FLASH_1 +0x20000) in my head file. but after link ,the environments are at the (PHYS_FLASH_1 + 0x15900) of ppcboot.bin instead?
__________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com
Dear Joe,
in message 20031021045845.85144.qmail@web41108.mail.yahoo.com you wrote:
the other problem is why I set the#define CFG_ENV_ADDR (PHYS_FLASH_1 +0x20000) in my head file. but after link ,the environments are at the (PHYS_FLASH_1 + 0x15900) of ppcboot.bin instead?
Because your board config file (the definitions of CFG_ENV_ADDR etc.) do not match the linker script u-boot.lds in your board directory?
Best regards,
Wolfgang Denk
participants (4)
-
Joe -
Rick Bronson -
Steven Scholz -
Wolfgang Denk