New IT forum
27 June 2022, 11:23:45 am *
Welcome, %1$s. Please login or register.

: CubieBoard 2 and Cubietruck both now in stock.
 
Pages: 1 [2]

Author Topic: GuruPlug don't boot the kernel anymore after re-flasing  (Read 31769 times)

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #15 on: 04 April 2011, 11:08:25 pm »

saveenv is only required if you are going to restart u-boot by eg. either running 'reset' or cycling the power to the plug.
When u-boot starts it copies the environment from NAND into RAM from where it is then referenced (so you would loose your changes if you hadn't saved them).

EDIT: It seems u-boot has a bug in that environment variables can get 'lost' (see the u-boot mail archives). It would be a good idea to do a 'printenv' to double check
*everything* is correct after making any changes before doing a 'saveenv'.
« Last Edit: 08 April 2011, 11:37:12 pm by Confusticated »
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

hardillb

  • Newbie
  • *
  • Posts: 1
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #16 on: 07 April 2011, 09:54:00 am »


I have temporarily another guruPlug, unmodified, so I used this other device to retrieve some files:
Code: [Select]
dd if=/dev/mtdblock1 of=uImage-GuruUnmodified

I'm in the same situation as you here and I've also managed to get my hands on a unadulterated plug to try and recover from.

I've run the command you mentioned above and I have couple of quick questions.

Code: [Select]
dd if=/dev/mtdblock1 of=uImage-GuruUnmodified
dd: reading `/dev/mtdblock1': Input/output error
1024+0 records in
1024+0 records out
524288 bytes (524 kB) copied, 0.771468 s, 680 kB/s

1) The file is only 512k which is a lot smaller than I was expecting (the other Kernel images where 2.6mb).  How big was the file you managed to generate?
2) I take it I should install this (assuming it's the right size) via tftp like I did with the newer versions of the kernel that broke me earlier?

I've also tried reading from /dev/mtd1 and /dev/mtd1ro both of which give a 4mb file.

Thanks
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #17 on: 08 April 2011, 11:30:33 pm »

Quote
dd: reading `/dev/mtdblock1': Input/output error
                                         ^^^^^^^^^
Burning this to the plug will most likely brick it
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

marxjohnson

  • Newbie
  • *
  • Posts: 7
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #18 on: 09 April 2011, 10:16:11 am »

Thanks for your help guys, but I'm still experiencing the same problem. My environment now looks like this:
Code: [Select]
bootdelay=3
baudrate=115200
ethaddr=F0:AD:4E:FF:11:65
filesize=B940000
fileaddr=6400000
ipaddr=192.168.0.9
serverip=192.168.0.2
x_bootcmd_usb=usb start
x_bootcmd_kernel=nand read.e 0x6400000 0x100000 0x400000
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootargs=console=ttyS0,115200
ethact=egiga0
bootcmd=setenv ethact egiga0; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm ;
stdin=serial
stdout=serial
stderr=serial

If you can give me any other pointers I'd be very grateful.
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #19 on: 09 April 2011, 08:15:32 pm »

try 'setenv machid 0x0A29'
« Last Edit: 09 April 2011, 08:19:04 pm by Confusticated »
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

marxjohnson

  • Newbie
  • *
  • Posts: 7
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #20 on: 11 April 2011, 05:15:25 pm »

Thanks for that Confusticated, still no joy though I'm afraid.  The only change is that I now get the message "Using machid 0x0a29 from environment" before "Starting Kernel".
Logged

NewITMalcolm

  • Administrator
  • Sr. Member
  • *****
  • Posts: 394
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #21 on: 11 April 2011, 05:37:55 pm »

Hi marxjohnson,

I don't have a Guru to hand at the moment to test this out but I am going to make some suggestions.

filesize=B940000
fileaddr=6400000

change to:

filesize=0xb940000
fileaddr=0x6400000

try changing bootm; to bootm 0x6400000;

If that's no help try my Guru reflashing technique here:

http://www.newit.co.uk/forum/index.php/topic,1810.0.html

NewIT Technical
Logged
NewITJames

marxjohnson

  • Newbie
  • *
  • Posts: 7
Re: GuruPlug don't boot the kernel anymore after re-flasing
« Reply #22 on: 17 April 2011, 09:09:35 am »

Success! I reflashed via USB using those instructions, made that change to the bootcmd and removed all the environment variables not listed on http://www.newit.co.uk/forum/index.php/topic,400.msg1610.html#msg1610
For the record, my environment now looks like this:
Code: [Select]
bootdelay=3
baudrate=115200
ethaddr=F0:AD:4E:FF:11:65
x_bootcmd_usb=usb start
x_bootcmd_kernel=nand read.e 0x6400000 0x100000 0x400000
x_bootargs_root=ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs
x_bootargs=console=ttyS0,115200
ethact=egiga0
bootcmd=setenv ethact egiga0; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
stdin=serial
stdout=serial
stderr=serial
eth1addr=02:50:43:f5:d4:ce
Thanks everyone for your help, your support is fantastic!
Logged
Pages: 1 [2]
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!