• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 ... 6 7 [8] 9 10 ... 16
Author Topic: Sheevaplug installer - version 1.0  (Read 99690 times)
truxntrax
Newbie
*

Karma: 0
Posts: 21


View Profile
« Reply #105 on: October 22, 2009, 03:02:48 PM »

All sorted now- I had the wrong files.  Everything worked ok after getting the correct files.  Thanks to those who helped.
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #106 on: October 23, 2009, 08:23:42 AM »

Code:
root@reedy-laptop:/home/reedy# screen /dev/ttyUSB1 115200
Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x400000

Bad block at 0x360000 in erase block from 0x360000 will be skipped
Reading data from 0x4f7000 --  96% complete.reading NAND page at offset 0x500000 failed
 4194304 bytes read: ERROR
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.30.2
   Created:      2009-07-23   1:53:36 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2620440 Bytes =  2.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
Marvell>>

Is that a memory stick or a plug problem?

Tried reformatting the memory stick and recopying the files, to no avail. Havent got another free memory stick atm to try.


Thanks


Sam
« Last Edit: October 23, 2009, 08:29:14 AM by Reedy » Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #107 on: October 24, 2009, 12:05:49 AM »

This is a bad block within your NAND flash which is in the plug.
The kernel image is being read from 0x100000 to 0x500000 and it looks like uboot found a bad block there.

You can change the uImage burn address to work around this.
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #108 on: October 24, 2009, 03:52:32 PM »

This is a bad block within your NAND flash which is in the plug.
The kernel image is being read from 0x100000 to 0x500000 and it looks like uboot found a bad block there.

You can change the uImage burn address to work around this.

Thanks, any hints on how to actually do that?
Logged

badcam
Jr. Member
**

Karma: 1
Posts: 78


View Profile
« Reply #109 on: October 25, 2009, 08:14:03 PM »

I'm getting the same "Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469" message that BP was getting, but I can't figure out how to prevent it. I'm trying to run this via Windows XP. I have the two Com ports showing. The only difference between the original Sheeva Installer V1.0 is that I have taken Roosters suggestion ( http://plugcomputer.org/plugforum/index.php?topic=734.msg4592#msg4592) to update the new kernal.

I note that someone else has this same issue: http://plugcomputer.org/plugforum/index.php?topic=872.0

[EDIT:] and another person with the same issue: http://plugcomputer.org/plugforum/index.php?topic=802.0

I found this thread which might be of help:

The answer seems to bein the last post perhaps:

http://forum.sparkfun.com/viewtopic.php?t=17504&sid=01ecd8881261826291cd3d6052bb04ad

"The latest OpenOcd does not support the FTDI drivers, you will to need unpack the file drivers/ft2232.zip and follow the instructions in "info.txt"."

I'll see where this takes me... [/EDIT]

If I could please have some suggestions. Thanks in advance:

Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Badcam>cd desktop/sheevainstall

C:\Documents and Settings\Badcam\Desktop\SheevaInstall>runme nand

 ****   Preparing environment variables file ...
reading uboot\uboot-env\uboot-dflt.txt
uboot\uboot-env\fw_setenv.exe baudrate 115200
CRC read error on uboot-env.bin: No error
uboot\uboot-env\fw_setenv.exe loads_echo 0
uboot\uboot-env\fw_setenv.exe ipaddr 10.4.50.165
uboot\uboot-env\fw_setenv.exe serverip 10.4.50.5
uboot\uboot-env\fw_setenv.exe rootpath /mnt/ARM_FS/
uboot\uboot-env\fw_setenv.exe netmask 255.255.255.0
uboot\uboot-env\fw_setenv.exe stdin serial
uboot\uboot-env\fw_setenv.exe stdout serial
uboot\uboot-env\fw_setenv.exe stderr serial
uboot\uboot-env\fw_setenv.exe console console=ttyS0,115200 mtdparts=nand_mtd:0xc
0000@0(uboot)ro,0x1ff00000@0x100000(root)
uboot\uboot-env\fw_setenv.exe mainlineLinux no
uboot\uboot-env\fw_setenv.exe CASset min
uboot\uboot-env\fw_setenv.exe enaMonExt no
uboot\uboot-env\fw_setenv.exe enaCpuStream no
uboot\uboot-env\fw_setenv.exe enaWrAllo no
uboot\uboot-env\fw_setenv.exe pexMode RC
uboot\uboot-env\fw_setenv.exe disL2Cache no
uboot\uboot-env\fw_setenv.exe setL2CacheWT yes
uboot\uboot-env\fw_setenv.exe disL2Prefetch yes
uboot\uboot-env\fw_setenv.exe enaICPref yes
uboot\uboot-env\fw_setenv.exe enaDCPref yes
uboot\uboot-env\fw_setenv.exe sata_dma_mode yes
uboot\uboot-env\fw_setenv.exe MALLOC_len 1
uboot\uboot-env\fw_setenv.exe ethprime egiga0
uboot\uboot-env\fw_setenv.exe netbsd_en no
uboot\uboot-env\fw_setenv.exe vxworks_en no
uboot\uboot-env\fw_setenv.exe bootargs_root root=/dev/nfs rw
uboot\uboot-env\fw_setenv.exe bootargs_end :::DB88FXX81:eth0:none
uboot\uboot-env\fw_setenv.exe image_name uImage
uboot\uboot-env\fw_setenv.exe bootcmd tftpboot 0x2000000 $(image_name);setenv bo
otargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):
$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;
uboot\uboot-env\fw_setenv.exe standalone fsload 0x2000000 $(image_name);setenv b
ootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end
) $(mvPhoneConfig); bootm 0x2000000;
uboot\uboot-env\fw_setenv.exe bootdelay 3
uboot\uboot-env\fw_setenv.exe disaMvPnp no
uboot\uboot-env\fw_setenv.exe ethaddr 00:50:43:4e:2a:14
uboot\uboot-env\fw_setenv.exe ethmtu 1500
uboot\uboot-env\fw_setenv.exe mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot\uboot-env\fw_setenv.exe mvNetConfig mv_net_config=(00:11:88:0f:62:81,0:1:2
:3),mtu=1500
uboot\uboot-env\fw_setenv.exe usb0Mode host
uboot\uboot-env\fw_setenv.exe yuk_ethaddr 00:00:00:EE:51:81
uboot\uboot-env\fw_setenv.exe nandEcc 1bit
uboot\uboot-env\fw_setenv.exe netretry no
uboot\uboot-env\fw_setenv.exe rcvrip 169.254.100.100
uboot\uboot-env\fw_setenv.exe loadaddr 0x02000000
uboot\uboot-env\fw_setenv.exe autoload no
uboot\uboot-env\fw_setenv.exe enaAutoRecovery yes
uboot\uboot-env\fw_setenv.exe ethact egiga0
reading uboot\uboot-env\uboot-nand-custom.txt
uboot\uboot-env\fw_setenv.exe bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstyp
e=ubifs
uboot\uboot-env\fw_setenv.exe mtdpartitions mtdparts=orion_nand:0x400000@0x10000
0(uImage),0x1fb00000@0x500000(rootfs)
uboot\uboot-env\fw_setenv.exe ethaddr 00:50:43:01:D5:8F
uboot\uboot-env\fw_setenv.exe real_bootcmd setenv bootargs $(bootargs_console) $
(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000;
bootm 0x00800000
uboot\uboot-env\fw_setenv.exe bootargs_console console=ttyS0,115200
uboot\uboot-env\fw_setenv.exe bootcmd run recover1
uboot\uboot-env\fw_setenv.exe recover1 setenv mainlineLinux yes; setenv arcNumbe
r 2097; setenv bootcmd run recover2; saveenv; reset
uboot\uboot-env\fw_setenv.exe recover2 run recover3; setenv bootcmd $(real_bootc
md); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram
0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
uboot\uboot-env\fw_setenv.exe recover3 run recover4; nand erase clean 0x00100000
 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
uboot\uboot-env\fw_setenv.exe recover4 usb start; fatload usb 0 0x00800000 uImag
e; fatload usb 0 0x01100000 initrd

 ****   Burning uboot and environment variables ... This will take few minutes .
..
 ****   When uboot.bin is written to NAND/SD, Disconnect and connect your mini U
SB cable
Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd
.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug
C:\Documents and Settings\Badcam\Desktop\SheevaInstall>runme nand

 ****   Preparing environment variables file ...
reading uboot\uboot-env\uboot-dflt.txt
uboot\uboot-env\fw_setenv.exe baudrate 115200
CRC read error on uboot-env.bin: No error
uboot\uboot-env\fw_setenv.exe loads_echo 0
uboot\uboot-env\fw_setenv.exe ipaddr 10.4.50.165
uboot\uboot-env\fw_setenv.exe serverip 10.4.50.5
uboot\uboot-env\fw_setenv.exe rootpath /mnt/ARM_FS/
uboot\uboot-env\fw_setenv.exe netmask 255.255.255.0
uboot\uboot-env\fw_setenv.exe stdin serial
uboot\uboot-env\fw_setenv.exe stdout serial
uboot\uboot-env\fw_setenv.exe stderr serial
uboot\uboot-env\fw_setenv.exe console console=ttyS0,115200 mtdparts=nand_mtd:0xc
0000@0(uboot)ro,0x1ff00000@0x100000(root)
uboot\uboot-env\fw_setenv.exe mainlineLinux no
uboot\uboot-env\fw_setenv.exe CASset min
uboot\uboot-env\fw_setenv.exe enaMonExt no
uboot\uboot-env\fw_setenv.exe enaCpuStream no
uboot\uboot-env\fw_setenv.exe enaWrAllo no
uboot\uboot-env\fw_setenv.exe pexMode RC
uboot\uboot-env\fw_setenv.exe disL2Cache no
uboot\uboot-env\fw_setenv.exe setL2CacheWT yes
uboot\uboot-env\fw_setenv.exe disL2Prefetch yes
uboot\uboot-env\fw_setenv.exe enaICPref yes
uboot\uboot-env\fw_setenv.exe enaDCPref yes
uboot\uboot-env\fw_setenv.exe sata_dma_mode yes
uboot\uboot-env\fw_setenv.exe MALLOC_len 1
uboot\uboot-env\fw_setenv.exe ethprime egiga0
uboot\uboot-env\fw_setenv.exe netbsd_en no
uboot\uboot-env\fw_setenv.exe vxworks_en no
uboot\uboot-env\fw_setenv.exe bootargs_root root=/dev/nfs rw
uboot\uboot-env\fw_setenv.exe bootargs_end :::DB88FXX81:eth0:none
uboot\uboot-env\fw_setenv.exe image_name uImage
uboot\uboot-env\fw_setenv.exe bootcmd tftpboot 0x2000000 $(image_name);setenv bo
otargs $(console) $(bootargs_root) nfsroot=$(serverip):$(rootpath) ip=$(ipaddr):
$(serverip)$(bootargs_end) $(mvNetConfig) $(mvPhoneConfig);  bootm 0x2000000;
uboot\uboot-env\fw_setenv.exe standalone fsload 0x2000000 $(image_name);setenv b
ootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end
) $(mvPhoneConfig); bootm 0x2000000;
uboot\uboot-env\fw_setenv.exe bootdelay 3
uboot\uboot-env\fw_setenv.exe disaMvPnp no
uboot\uboot-env\fw_setenv.exe ethaddr 00:50:43:4e:2a:14
uboot\uboot-env\fw_setenv.exe ethmtu 1500
uboot\uboot-env\fw_setenv.exe mvPhoneConfig mv_phone_config=dev0:fxs,dev1:fxs
uboot\uboot-env\fw_setenv.exe mvNetConfig mv_net_config=(00:11:88:0f:62:81,0:1:2
:3),mtu=1500
uboot\uboot-env\fw_setenv.exe usb0Mode host
uboot\uboot-env\fw_setenv.exe yuk_ethaddr 00:00:00:EE:51:81
uboot\uboot-env\fw_setenv.exe nandEcc 1bit
uboot\uboot-env\fw_setenv.exe netretry no
uboot\uboot-env\fw_setenv.exe rcvrip 169.254.100.100
uboot\uboot-env\fw_setenv.exe loadaddr 0x02000000
uboot\uboot-env\fw_setenv.exe autoload no
uboot\uboot-env\fw_setenv.exe enaAutoRecovery yes
uboot\uboot-env\fw_setenv.exe ethact egiga0
reading uboot\uboot-env\uboot-nand-custom.txt
uboot\uboot-env\fw_setenv.exe bootargs_root ubi.mtd=1 root=ubi0:rootfs rootfstyp
e=ubifs
uboot\uboot-env\fw_setenv.exe mtdpartitions mtdparts=orion_nand:0x400000@0x10000
0(uImage),0x1fb00000@0x500000(rootfs)
uboot\uboot-env\fw_setenv.exe ethaddr 00:50:43:01:D5:8F
uboot\uboot-env\fw_setenv.exe real_bootcmd setenv bootargs $(bootargs_console) $
(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000;
bootm 0x00800000
uboot\uboot-env\fw_setenv.exe bootargs_console console=ttyS0,115200
uboot\uboot-env\fw_setenv.exe bootcmd run recover1
uboot\uboot-env\fw_setenv.exe recover1 setenv mainlineLinux yes; setenv arcNumbe
r 2097; setenv bootcmd run recover2; saveenv; reset
uboot\uboot-env\fw_setenv.exe recover2 run recover3; setenv bootcmd $(real_bootc
md); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram
0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
uboot\uboot-env\fw_setenv.exe recover3 run recover4; nand erase clean 0x00100000
 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
uboot\uboot-env\fw_setenv.exe recover4 usb start; fatload usb 0 0x00800000 uImag
e; fatload usb 0 0x01100000 initrd

 ****   Burning uboot and environment variables ... This will take few minutes .
..
 ****   When uboot.bin is written to NAND/SD, Disconnect and connect your mini U
SB cable
Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd
.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug
C:\Documents and Settings\Badcam\Desktop\SheevaInstall>

« Last Edit: October 25, 2009, 08:46:52 PM by badcam » Logged

cagey76
Newbie
*

Karma: 0
Posts: 3


View Profile
« Reply #110 on: October 25, 2009, 11:25:39 PM »

I am having real problems getting the installer to install,  I get as far as the error messgae below, and just can't seem to get past it. I have spent hours searching the forums and trying everything. I have tried many different orders of connecting, changed the cfg file as suggested etc.

Any help would be appreciated.


C:\TEMP\sheevaplug-installer-v1.0>runme.exe nand | mmc
CRC read error on uboot-env.bin: No error
Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd
.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
Logged

rooster
Administrator
Sr. Member
*****

Karma: 8
Posts: 311


View Profile
« Reply #111 on: October 26, 2009, 01:43:00 AM »

If you are using the installer do the following:
change the following sheevaplug-installer-v1.0/uboot/uboot-env/uboot-nand-custom.txt
1)
from: mtdpartitions mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
to:    mtdpartitions mtdparts=orion_nand:0x400000@0x200000(uImage),0x1fb00000@0x600000(rootfs)
2)
from: recover3 run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
to:    recover3 run recover4; nand erase clean 0x00200000 0x00400000; nand write.e 0x00800000 0x00200000 0x00400000
3)
from: real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
to:    real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00200000 0x00400000; bootm 0x00800000

These changes should skip the first mega of nand flash nd burn the uImage in offset 2MB and also burn the correct uboot parameters for uboot to boot from.
Logged

badcam
Jr. Member
**

Karma: 1
Posts: 78


View Profile
« Reply #112 on: October 26, 2009, 02:41:46 AM »

So sorry, but I'm still getting the same error.

Hopefully cagey76 will have better success.

[EDIT] Sorry. Forgot to add; Thanks for your suggestion Rooster. I'll try it again tomorrow when I feel a bit fresher.  Grin
« Last Edit: October 26, 2009, 02:52:44 AM by badcam » Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #113 on: October 26, 2009, 04:28:46 AM »

I am having real problems getting the installer to install,  I get as far as the error messgae below, and just can't seem to get past it. I have spent hours searching the forums and trying everything. I have tried many different orders of connecting, changed the cfg file as suggested etc.

Any help would be appreciated.


C:\TEMP\sheevaplug-installer-v1.0>runme.exe nand | mmc
CRC read error on uboot-env.bin: No error
Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd
.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:

Why are you trying to Or Nand and MMC?

Its one OR the other.. for a start Wink

runme.exe nand

OR

runme.exe mmc
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #114 on: October 26, 2009, 04:30:09 AM »

If you are using the installer do the following:
change the following sheevaplug-installer-v1.0/uboot/uboot-env/uboot-nand-custom.txt
1)
from: mtdpartitions mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
to:    mtdpartitions mtdparts=orion_nand:0x400000@0x200000(uImage),0x1fb00000@0x600000(rootfs)
2)
from: recover3 run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
to:    recover3 run recover4; nand erase clean 0x00200000 0x00400000; nand write.e 0x00800000 0x00200000 0x00400000
3)
from: real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
to:    real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00200000 0x00400000; bootm 0x00800000

These changes should skip the first mega of nand flash nd burn the uImage in offset 2MB and also burn the correct uboot parameters for uboot to boot from.

Thanks Smiley

Will have a poke this afternoon
Logged

cagey76
Newbie
*

Karma: 0
Posts: 3


View Profile
« Reply #115 on: October 26, 2009, 10:21:27 AM »

reedy,   hehe,  good shout cheers.  I have now tried with just nand and have got further.

rooster,  I have tried the changes you suggested, but still no joy, error message below.  I have to log onto the sheeva via putty to stop uboot before I try the runme, presume this is correct.

thanks for the responses, appreciate the help.


-------------------------------------------------------------------------------------------------------------------

 ****   Burning uboot and environment variables ... This will take few minutes .
..
 ****   When uboot.bin is written to NAND/SD, Disconnect and connect your mini U
SB cable
Open On-Chip Debugger 0.2.0 (2009-07-27-16:41) Release
$URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd
.c $
For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
2000 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
dcc downloads are enabled
Error: unable to open ftdi device: device not found
Runtime error, file "command.c", line 469:
     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug
Logged

badcam
Jr. Member
**

Karma: 1
Posts: 78


View Profile
« Reply #116 on: October 26, 2009, 12:33:19 PM »

     ****       openocd FAILED
 ****   Is the mini USB cable connected?
 ****   Try powering down, then replugging the Sheevaplug

So it looks like you're at the same point that I am.  Cheesy

Did you try Rooster's suggestion as follows  Huh :

If you are using the installer do the following:
change the following sheevaplug-installer-v1.0/uboot/uboot-env/uboot-nand-custom.txt
1)
from: mtdpartitions mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
to:    mtdpartitions mtdparts=orion_nand:0x400000@0x200000(uImage),0x1fb00000@0x600000(rootfs)
2)
from: recover3 run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
to:    recover3 run recover4; nand erase clean 0x00200000 0x00400000; nand write.e 0x00800000 0x00200000 0x00400000
3)
from: real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
to:    real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00200000 0x00400000; bootm 0x00800000

These changes should skip the first mega of nand flash nd burn the uImage in offset 2MB and also burn the correct uboot parameters for uboot to boot from.
Logged

cagey76
Newbie
*

Karma: 0
Posts: 3


View Profile
« Reply #117 on: October 26, 2009, 01:00:28 PM »

badcam,  yep I have tried the suggestion from rooster,  but it didn't work. 
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #118 on: October 26, 2009, 05:17:11 PM »

I think those were for me, as i was having some actual flashing issues Smiley
Logged

Reedy
Newbie
*

Karma: 0
Posts: 40


View Profile
« Reply #119 on: October 26, 2009, 05:54:57 PM »

If you are using the installer do the following:
change the following sheevaplug-installer-v1.0/uboot/uboot-env/uboot-nand-custom.txt
1)
from: mtdpartitions mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
to:    mtdpartitions mtdparts=orion_nand:0x400000@0x200000(uImage),0x1fb00000@0x600000(rootfs)
2)
from: recover3 run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
to:    recover3 run recover4; nand erase clean 0x00200000 0x00400000; nand write.e 0x00800000 0x00200000 0x00400000
3)
from: real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
to:    real_bootcmd setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root); nand read.e 0x00800000 0x00200000 0x00400000; bootm 0x00800000

These changes should skip the first mega of nand flash nd burn the uImage in offset 2MB and also burn the correct uboot parameters for uboot to boot from.

Didn't actually seem to work, so i changed them back, reflashed, and it works

Thanks rooster! Smiley
Logged

Pages: 1 ... 6 7 [8] 9 10 ... 16
Print
Jump to: