i.MX53 JSK with wce, no boot after envreset in uboot

Embedded Devices Windows CE
,
1

My i.MX53 JSK with wce was working perfectly, but after a envreset in the uboot, the system will not boot, but stops in uboot after “autoscript from TPTF…[not avaible]” - and does not come with “hit any key to stop autoboot”

I did set the missing env’s, but it is not helping - what am I missing?

bootdelay=4
baudrate=115200
loadaddr=0x70800000
silent=no
ethprime=FEC0
ethact=FEC0
wdmode=1
bootcmd=dboot wce flash
ldb=single, di=0,ch0_map=SPWG
video2=displayfb:disable
fbprimary=video
video=displayfb:LCD@LQ070Y3DG3B
ethaddr=00:40:9D:6A:1C:B6
wlanaddr=00:40:9D:6A:1F:EB
eth1addr=00:40:9D:6A:1C:CF
btaddr=00:00:00:00:00:00
ipaddr=192.168.42.30
ipaddr_wlan=192.168.43.30
ipaddr1=192.168.44.30
netmask=255.255.255.0
netmask_wlan=255.255.255.0
netmask1=255.255.255.0
serverip=192.168.42.1
gatewayip=0.0.0.0
dnsip=0.0.0.0
dnsip2=0.0.0.0
dhcp=off
dhcp_wlan=off
dhcp1=off
mtdids=nand0=onboard_boot
mtdparts=mtdparts=onboard_boot:0x100000(U-Boot),0x80000@0x100000(NVRAM),0x280000
0@0x180000(Kernel),0x1d680000@0x2980000(Filesys)
hostname=CCWMX53-6A1CB6
stdin=serial
stdout=serial
stderr=serial

console=console=ttymxc0,115200
androidloadaddr=0x70800000
aimg=uImage-android-ccwmx53js
ebootaddr=0x70800000
eimg=eboot-CCXMX53
sata_rpart=/dev/sda2
hostname=CCWMX53-6A1CB6
ip=ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:eth0:off
loadaddr=0x70800000
loadaddr_initrd=CONFIG_INITRD_LOAD_ADDR
kimg=uImage-ccwmx53js
npath=/exports/nfsroot-ccwmx53js
linuxloadaddr=0x70800000
loadzipaddr=CONFIG_ZIP_LOAD_ADDR
loadbootsc=yes
bootscript=ccwmx53js-bootscript
mmc_rpart=/dev/mmcblk0p2
netosloadaddr=CONFIG_NETOS_LOAD_ADDR
rimg=
arimg=
rootdelay=10
smtd=
snfs=root=nfs nfsroot=${serverip}:
std_bootarg=
uimg=u-boot-ccwmx53js.bin
usrimg=userfs-ccwmx53js-128.jffs2
video=displayfb:LCD@LQ070Y3DG3B
video2=displayfb:disable
wceloadaddr=0x74000000
wimg=wce-CCXMX53
wzimg=wcez-CCXMX53

2

You need to set the serverip address.to dowloand your image using TFTP.
Below is an explanation of how the booloader works, you can find this info in the bootloaders manual link below:
http://ftp1.digi.com/support/documentation/90001129_B.pdf

The bootscript works in the following way:

  1. U-Boot checks the variable loadbootsc. If set to “no”, it continues its normal execution.
  2. If the variable loadbootsc is set to “yes” (factory default value) U-Boot tries to download the bootscript file with the filename stored in variable bootscript from the TFTP server IP address defined at variable serverip (by default 192.168.42.1).
    The default value of the bootscript variable is -bootscript.
  3. If the bootscript file is successfully downloaded, it is executed.
  4. If any of the commands in the bootscript fails, the rest of the script is cancelled.
  5. When the bootscript has been fully executed (or cancelled) U-Boot continues normal execution.
3

Try to boot manually.

ie: execute dboot wce flash in uboot prompt

4

Hi Tuxembb

Execute dboot wce flash in uboot prompt manuelly works, but I would like it to do it automatically, just as it was before I run the envreset in uboot.

Hi Campbell

I want to use the image which is already on the internally flash.

5

Hi

I solved the problem

for any reason???, the environment variable “bootcmd=dboot wce flash” was not correct, setting it again (so I have two which are exactly the same seen with printenv) then it is working with autoboot from flash.