|
Hi all!
I am totally stuck on a prototype board very similar to AT91SAM9RL-EK.
Trial 1: I downloaded the different linux4sam binary packages and followed the written explanations, tips and hints... My board doesn't have Dataflash, so I use NAND, started SAMBA 2.10 and got a connection. EEPROM access works, internal SRAM works too. But enabling the SDRAM results in hangup of SAMBA. Enabling NAND Flash results in hangup of SAMBA. Both times I can kill SAMBA and restart it most times without any problem. Some times I had to powercycle the board. So no way to flash it with SAMBA.
Trial 2: Using OpenOCD-0.4.0 I cannot get rid of the RTCK not supproted message and it falls down to 5kHz JTAG speed. So trying to upload an uBoot to SRAM is nearly impossible if you don't wait a night for the upload. But I can control the CPU. There was no at91sam9rl.cfg so I made one, like I did it for many other CPUs. Never got that RTCK error message.
Trial 3: The SRAM I have on my board are probably not the same as the ones on the -EK. So I adapted the settings in the extram section of SAMBA and recompiled the code. The linke threw me out with multiple definition of _impure_ptr but I go rid of that by adding -nostartfiles to the linker. But with the resulting binary SAMBA now doesn't start completely. It appears in the taskmanager, consumes 100% CPU load but doesn't show up.
Now I am stuck.
Is there anyone to help me get out of this deadlock? Only one simple method of getting uBoot onto the board would fit. I would love openocd but SAMBA will do either. Or if there is an option to put everything needed to boot linux on a single SD-Card it would be fine too.
The chip is a AT91SAM9RL64 SDRAM is EDS2516AFTA, looks similar to MF48LC16M16A2P NAND is K9F1G08U0C All memories are connected to the same control lines and chip selects as on the RL-EK.
Many thanks in advance and best regards Ulrich
|