Hello,
I have had the same problem with the deploy-script for PicoCom1.
My solution: To use only the first part of the deploy-script. The remaining parts
should be commented out:
Code
- ...
- ...
- copy_images
- flash_uboot_steppingstone
- # environment
- uboot_cmd "setenv serverip $SERVER_IP" 1
- uboot_cmd "setenv ipaddr $BOARD_IP" 1
- # uboot
- # uboot_cmd "tftpboot 0x20000000 $BOARD_NAME.uboot" 120
- # uboot_cmd "nand erase 0x8000 0x3ffff" 120
- # uboot_cmd "nand write 0x20000000 0x8000 \${filesize}" 120
- # kernel
- # uboot_cmd "tftpboot 0x20000000 $BOARD_NAME.kernel" 120
- # uboot_cmd "nand erase clean 0x100000 0x17ffff" 120
- # uboot_cmd "nand write.jffs2 0x20000000 0x100000 \${filesize}" 120
- # dat
- # uboot_cmd "tftpboot 0x20000000 $BOARD_NAME.data" 120
- # uboot_cmd "nand erase clean 0x50000 0xaffff" 120
- # uboot_cmd "nand write.jffs2 0x20000000 0x50000 \${filesize}" 120
- # targetfs
- # uboot_cmd "tftpboot 0x20000000 $BOARD_NAME.targetfs" 600
- # uboot_cmd "nand erase clean 0x280000 0x1d7ffff" 120
- # uboot_cmd "nand write.jffs2 0x20000000 0x280000 \${filesize}" 240
- uboot_cmd "save"
- exp_send_user "$BOARD_NAME successfull flashed\n"
The procedure is as follows:
1) modify the deploy-script
2) run the deploy-script: ./deploy
3) start the PicoCom1 again
4) connect via kermit
5) set and save the environment variables (ethaddr, ipaddr, netmask, serverip)
6) do the remaining transfers with the following u-boot-commands:
run update.uboot
run update.kernel
run update.data
run update.targetfs
Müller
