Re: [Ltib] P2020ds Target deployment through a Windows system

[Peter Barada]

On Thu, 2010-05-20 at 10:33 -0500, Shila Haque wrote:
>     Hi,
>     
>     I have gone through the BSP user manual for P2020DS board and would appreciate if you could answer a question on the deployment of the target image to the P2020DS board. Presently, the P2020DS board that we are using can not be directly hooked up to the Linux computer (that built the target image on Fedora 12) directly. A Window's XP desktop is hooked up to the P2020DS board through a serial port. I created a RAMdisk image in LTIB using Linux pc and then transfer all necessary files( u-boot.bin, uImage, rootfs.ext2.gz.uboot,  p2020ds.dtb and others) to windows pc (at C:\tftpboot folder) using FileZilla. I connected the windows machine to the serial port 0, the settings for it are (115200, 8/N/1). I used tftpd32 and tried to flash U-boot trough hyperterminal session using following commands :
>     
>     => tftp 1000000 u-boot.bin
>     Speed: 100, half duplex
>     Using eTSEC1 device
>     TFTP from server 172.20.131.103; our IP address is 172.20.133.20; sending throug
>     h gateway 172.20.133.1
>     Filename 'u-boot.bin'.
>     Load address: 0x1000000
>     Loading: #################################################################
>              ######################################
>     done
>     Bytes transferred = 524288 (80000 hex)
>     => protect off all
>     Un-Protect Flash Bank # 1
>     => erase eff80000 efffffff
>     .... done
>     Erased 4 sectors
>     => cp.b 1000000 eff80000 $filesize
>     Copy to Flash... 9....8....7....6....5....4....3....2....1....done
>     =>
>     
>     Then reset the board to boot it up and tried to ramdisk deployment from TFTP. I set u-boot environment at u-boot prompt like as follows:
>     
>     =>setenv ipaddr 172.20.133.20
>     =>setenv serverip 172.20.131.103
>     =>setenv gatewayip 172.20.133.1
>     =>setenv bootargs root=/dev/ram rw console=ttyS0,115200
>     =>saveenv
>     Saving Environment to Flash...
>     Un-Protected 1 sectors
>     Erasing Flash...
>     . done
>     Erased 1 sectors
>     Writing to Flash... 9....8....7....6....5....4....3....2....1....done
>     Protected 1 sectors
>     
>     I am not sure about 'console=ttyS0' since I am using a windows pc as host. I also tftp uImage( at ec000000), p2020ds.dtb( at eff00000) and rootfs.ext2.gz.uboot ( at 10000000). I got the error as following:
>     
>     => boot
>     
Hmm, can you execute "printenv" in u-boot and post the result here?  Your bootcmd looks to be trying to load uImage and p202ds.dtb off of a SCSI device:
>     Loading file "uImage" from scsi device 0
>     Failed to mount ext2 filesystem...
>     ** Bad ext2 partition or disk - scsi 0:0 **
>     Loading file "p2020ds/p2020ds.dtb" from scsi device 0
>     Failed to mount ext2 filesystem...
>     ** Bad ext2 partition or disk - scsi 0:0 **
>     WARNING: adjusting available memory to 30000000
>     ## Booting kernel from Legacy Image at 01000000 ...
>        Image Name:   Linux-2.6.30
>        Image Type:   PowerPC Linux Kernel Image (gzip compressed)
>        Data Size:    3004778 Bytes =  2.9 MB
>        Load Address: 00000000
>        Entry Point:  00000000
>        Verifying Checksum ... OK
>     ERROR: Did not find a cmdline Flattened Device Tree
>     Could not find a valid device tree
>     
>     Can you please tell me the steps about how I will tftp 'uImage' and 'p2020ds.dtb' file along with u-boot.bin and which address should I use?

As for p2020-specifics, I can't help you as I've never played with that board...

>     
>     I would appreciate your feedback.
>     
>     Thanks,
>     
>     Shila
>     
> _______________________________________________
> LTIB home page: http://ltib.org
>
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib