- This topic has 0 replies, 1 voice, and was last updated 2 weeks, 2 days ago by .
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
- You must be logged in to reply to this topic.
Homepage › Forums › Modular Dev Kits › Q&A › Unable to retrieve uImage from TFTP server.
(This message was transferred over from our old forum)
Posted August 17, 2015
By Todd DeBoer
[hr]
On 10/14/09 rpicado asked, “I have an ARM9DIMM TS kit. I am able to retrieve uImage from a tftp server.
I have configured the serverip address and the boards ip address as well. It can ping the ftp server.
When the boot starts, the console shows a
“Loading #T T #T..
Retry Count Exceeded”
By using wireshark on teh TFTP server, it seems like the ARM9DIMM client connects to the server and start transferring datablocks. The server sends a data-block and the ARM9DIMM answers with a Ack
After the server sends block 138 (for instance, around a 11% size of the file) the ARM9DIMM request another “Read Request”, it does not send a block-138 ack. The servers acks that “Read Request”. Then the ARM9DIM re-sends a couple Block-0 acks (?) However the sever re-sends a data-block 138, and after that it sends a Error code to the ARM9 “invalid op code”
Then the whole process starts over.”
[hr]
(Follow up post)
Answered:
Use command “./ltib -m prep -p u-boot” to setup the u-boot source code in the rpm/BUILD already if not already done.
Then open file rpm/BUILD/u-boot-1.3.3/board/arm9dimm3250/arm9dimm3250.c. Add to the end of function reset_timer() the line “TIMER_CNTR0->mcr = 0”. Recompile and download.
TFTP should now work.
The SIBL bootloader is leaving the MCR in a different state than power up and the u-boot code is expecting it to be 0.
This change will be integrated when we release our next patch.