Hello,
at this moment, i use the ATK Toolkit 1.71 to program the XLDR.nb0 and the Eboot.nb0 to the i.MX. The Kernel, i am programing with Platform builder to the i.MX. This is working fine.
But in future, the programming of our board will do some guys in production department. Because these guys did not have Platform Builder, they have to use the ATK to program the nk.nb0 to i.MX.
I tested now the programming of the Kernel with ATK and have now the problem, that the Kernel will not load from NAND-Flash to RAM and so, the Kernel will not start. What could be my fault of thinking?
For some helpfull answers i will much obliged!
Greetings,
Norbert
The NK file cannot be downloaded with ATK tool.
To deploy images You may try ideas, suggested in the topic, linked below.
("Flashing a Windows CE 5.0 Device Without Using Platform Builder")
http://msdn2.microsoft.com/en-us/library/aa446908.aspx
The following should be done for it:
1.
We should apply TFTP client program, that may be configured for different ports
(standard TFTP port is 69). As was mentioned in the topic, the TFTP server in
the EBOOT boot loader uses non-standard TFTP port 980.
For example, WinAgents TFTP Client program may be used.
http://www.winagents.com/en/products/tftp-client/index.php
2.
EBOOT bootloader file ("Eboot.nb0") may be loaded and run on the board, using
external JTAG debugger or ATK toolkit
3.
Configure EBOOT to use static (non-DHCP) IP address, say, 192.168.2.75.
4.
Select EBOOT option "D) Download image now".
5.
Run tftp.exe to send the CE image (NK.BIN) to the board's IP address as follows:
"TFTP1 -i -p980 192.168.2.75 PUT BOOT.BIN".
Any file (in WinCE .bin format) to be loaded via EBOOT should be renamed as
"BOOT.BIN".
Hello Mr. Muhin,
thank you for your answer! Yesterday, I found in the Web a program CeLoader.exe, which is solving my problem!
Bye and with best regards,
Norbert Peter