Hi,

I cannot flash a demo on my AT91SAM9M10-EKES board.
When i run the .bat file logfile pops up immediately and show the following text:
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.10 on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : \usb\ARM0
-I- argv 1 : AT91SAM9M10-EK
-I- argv 2 : at91sam9m10ekes_demo_linux_nandflash.tcl
-E- Board at91sam9m10-ek not found
-E- Supported boards : at91sam3n2-ek at91sam7a3-ek at91sam9m10-g45-ek ...

whats with the line "-E- Board at91sam9m10-ek not found" ? I have EKES board. I even tried to run the .bat file for the EK board but of course it returns that i am not using the correct board.

Thanks for your help,

Best regards,

Janez

When you run SAM-BA manually, is your device '\usb\ARM0' ? and if you select your board 'AT91SAM9M10-EKES' does it connect ? if so just alter the batch file with notepad and change it. If its the wrong device (ie using CDC version) change that. Or just look at the batch file and flash the regions manually, the batch file is just there to be convenient.

I can connect to the board through SAM-BA. But when i try to execute the script from there i get this error:
Script error: could not read "uImage-2.6.30-r1-at91sam9m10ekes.bin": no such file or directory

I also tried to flash the regions manually but the linux doesnt load. In the TCL script i see u have to set some u-boot variables. Can you give a description how i exactly i need to flash regions manually, because if i just send all files to the board it doesnt work.

Best regards,

Janez

Hi,

I am able to connect on the board through SAM-BA. But when i try to execute the TCL script i get this error:
-E- Script error: could not read "uImage-2.6.30-r1-at91sam9m10ekes.bin": no such file or directory

I have also tried to flash the regions manually but the linux doesnt load. I see in the script it sets some u-boot variables. Can u give me a guide how to flash the regions manually correctly. If i just send all files to the board it doesnt work.
Thanks for your help.

Best regards,

Janez

For me, using sam-ba in linux with a tcl script, when you specify the files with no paths, they are relative to the current working directory you executed sam-ba from. I assume your problem is the same in windows.

Just edit the tcl script and change stuff like

set kernelFile "uImage-2.6.30-r1-at91sam9m10g45ek.bin"

to

set kernelFile "c:\mybuilddir\demo\uImage-2.6.30-r1-at91sam9m10g45ek.bin"

Basically your converting it from relative paths to absolute paths.
I'm not sure if you have to double escape the backslashes like this:

set kernelFile "c:\\mybuilddir\\demo\\uImage-2.6.30-r1-at91sam9m10g45ek.bin"

or not. Try the first way. Otherwise the only way I see it working is putting the bins in the dir with the sam-ba executable, or modifying the windows short cut to change the current working directory to your build directory.

I have already used absolute path. Didnt work. I will move the bins into the SAM-BA directory tommorow. Maybe that helps...
Thanks!

Best regards.

I can try booting up windows and trying it from there to see if I can reproduce your problem. I would also suggest running sam-ba manually, hitting browse and looking at which dir its in, that's probably the dir it's going to want the bins to be in for relative, that or the dir the tcl script is in.

If you don't get it going tomorrow I'll boot into windows so I can help.

Good luck.

It works now. I had to put bin files and scripts into the SAM-BA directory.
Thanks for your help.

Best regards,

Janez