Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« on: May 18, 2010, 07:54:20 AM » |
|
Hi, i have recived my new sheeva plug today and i have upgrade uboot to the last version but after do this the sheeva don't turn on it keeps with the green light turn on but i can't acces to it by serial or sy telnet or ssh and i don't know whats the problem the uboots seems to upgrade well , after upgrade i type reset and don't response more.
|
|
|
|
|
Logged
|
|
|
|
|
Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« Reply #1 on: May 18, 2010, 09:40:25 AM » |
|
now i'm trying to recover it using sheeva installer but i give the error: unable to open ftdi device, i have check the vip and pid on the device manager but it don't solve the issue please anybody can help me
edit: finally i can fix this issues, the problem was that i don't disable the filter with libusb, but now i have another error: Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (mfg: 0x1e9, part: 0x 0a02, ver: 0x2) Info : JTAG Tap/device matched target state: halted target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x600000d3 pc: 0x10000960 MMU: disabled, D-Cache: disabled, I-Cache: disabled target state: halted target halted in ARM state due to debug-request, current mode: Supervisor cpsr: 0x000000d3 pc: 0xffff0000 MMU: disabled, D-Cache: disabled, I-Cache: disabled 0 0 1 0: 00052078 NAND flash device 'NAND 512MiB 3,3V 8-bit' found Error: erase operation didn't pass, status: 0xc1 erase failed
|
|
|
|
« Last Edit: May 18, 2010, 10:00:26 AM by Guber1 »
|
Logged
|
|
|
|
|
Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« Reply #2 on: May 18, 2010, 10:42:07 AM » |
|
finally i get it works, after the erase error it writes and then the sheeva works ok
|
|
|
|
|
Logged
|
|
|
|
|
Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« Reply #3 on: May 19, 2010, 12:59:07 AM » |
|
i see on the uboot starts something strange :
T T T T T T T T T T Retry count exceeded; starting again ## Booting image at 02000000 ... Bad Magic Number Unknown command '<NULL>' - try 'help' Marvell>>
what's mean this? are something wrong?
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #4 on: May 19, 2010, 01:07:26 AM » |
|
it tries to get a Bootimage from a tftpserver and times out. Then it tries to load an image from internal flash at adress 0x200000 and doesn't find one. Next it runs an unknown command.
Show the output of "printenv" to get more help.
|
|
|
|
|
Logged
|
|
|
|
|
Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« Reply #5 on: May 19, 2010, 02:31:06 AM » |
|
USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 Marvell>> Marvell>> printenv baudrate=115200 loads_echo=0 ipaddr=10.4.50.165 serverip=10.4.50.5 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root) CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_end=:::DB88FXX81:eth0:none image_name=uImage standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000; ethaddr=00:50:43:06:01:06 ethmtu=1500 mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode=host yuk_ethaddr=00:00:00:EE:51:81 nandEcc=1bit netretry=no rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no arcNumber=2097 ethact=egiga0 bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root) root=/dev/nfs rw nfsroot=10.4.50.5:/mnt/ARM_FS/ ip=10.4.50.165:10.4.50.5:::DB88FXX81:eth0:none mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 mv_phone_config=dev0:fxs,dev1:fxs bootargs_console=console=ttyS0,115200 bootargs_root=root=/dev/mmcblk0p2 bootcmd_mmc=mmcinit; ext2load mmc 0:1 0x01100000 /uInitrd; ext2load mmc 0:1 0x00800000 /uImage bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_mmc; bootm 0x00800000 0x01100000 stdin=serial stdout=serial stderr=serial mainlineLinux=yes enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no bootdelay=3 disaMvPnp=no enaAutoRecovery=yes
Environment size: 1592/131068 bytes Marvell>>
here are the printenv i must say that i have try to install debian on a mmc
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #6 on: May 19, 2010, 03:05:41 AM » |
|
this env is not consistent with the error message you posted before. This is the interesting part. bootargs_console=console=ttyS0,115200 bootargs_root=root=/dev/mmcblk0p2 bootcmd_mmc=mmcinit; ext2load mmc 0:1 0x01100000 /uInitrd; ext2load mmc 0:1 0x00800000 /uImage bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_mmc; bootm 0x00800000 0x01100000
You can run it step by step at the u-boot prompt to find the error. (without my comments) setenv bootargs $(bootargs_console) $(bootargs_root) # configure the parameters that will be passed to the kernel mmcinit # initialize SD card ext2load mmc 0:1 0x01100000 /uInitrd # load ramdisk from sd card to memory address ext2load mmc 0:1 0x00800000 /uImage # load kernel from sd card to memory address bootm 0x00800000 0x01100000 # start kernel with ramdisk
|
|
|
|
|
Logged
|
|
|
|
|
Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« Reply #7 on: May 19, 2010, 11:51:12 AM » |
|
why did you say that it not consistent?, y can have troubles with this?, now and i out of home when i arrive home try these commands. Thanks
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #8 on: May 19, 2010, 01:31:44 PM » |
|
because the errors you posted show tftp timeouts and a boot from a different memory address. your u-boot env only does the steps i posted.
|
|
|
|
|
Logged
|
|
|
|
|
Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« Reply #9 on: May 19, 2010, 01:51:43 PM » |
|
if i do the steps that you say debian boots from mi sd card, i really don't understand what it's the problem
|
|
|
|
|
Logged
|
|
|
|
|
|
|
 |
« Reply #10 on: May 19, 2010, 02:08:52 PM » |
|
so reset plug, interrupt at the boot, check the env and simply run "boot". if this doesn't work it might be a timing issue with mmcinit. reset, interrupt, run mmcinit, count to 10, then run boot.
|
|
|
|
|
Logged
|
|
|
|
|
Guber1
Newbie
Karma: 0
Posts: 24
|
 |
« Reply #11 on: May 19, 2010, 02:12:14 PM » |
|
if i reset an interupt the boot, then type boot and also debian starts.
|
|
|
|
|
Logged
|
|
|
|
|
|