New IT forum
26 June 2022, 04:45:25 pm *
Welcome, %1$s. Please login or register.

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

Author Topic: Dreambrick... Uboot environment flash??? [SOLVED]  (Read 6447 times)

DS

  • Newbie
  • *
  • Posts: 4
Dreambrick... Uboot environment flash??? [SOLVED]
« on: 30 November 2013, 07:20:08 pm »

Has anyone actually managed to update the uboot boot environment without bricking their dreamplug?

I followed the process of upgrading uboot as detailed in the following links.

https://github.com/nickdaly/freedom-maker
http://www.josegaert.com/blog/learning-the-basics-of-das-u-boot-with-the-globalscale-technologies-dreamplug
http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/

After upgrading, the dreamplug fails to boot. I am able to get the dreamplug to load the uboot environment using kwuartboot, but after flashing the device with the new u-boot.kwb from newit as soon as I reset the device it fail to boot and the console screen is blank.

Some advice would be very much appreciated before I end up tossing it in the bin.



Code: [Select]
U-Boot 2011.09-rc1-00001-g2a0acfc-dirty (Sep 12 2011 - 19:33:35)
Marvell-DreamPlug

SoC:   Kirkwood 88F6281_A1
DRAM:  512 MiB
WARNING: Caches not enabled
SF: Detected MX25L1605D with page size 64 KiB, total 2 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0, egiga1
88E1116 Initialized on egiga0
88E1116 Initialized on egiga1
Hit any key to stop autoboot:  0
Marvell>>

Marvell>> printenv
baudrate=115200
bootcmd=setenv ethact egiga0; ${x_bootcmd_ethernet}; setenv ethact egiga1; ${x_bootcmd_ethernet}; ${x_bootcmd_usb}; ${x_bootcmd_kernel}; setenv bootargs ${x_bootargs} ${x_bootargs_root}; bootm 0x6400000;
bootdelay=3
eth1addr=F0:AD:4E:00:7E:FC
ethact=egiga0
ethaddr=F0:AD:4E:00:7E:FB
stderr=serial
stdin=serial
stdout=serial
x_bootargs=console=ttyS0,115200
x_bootargs_root=root=/dev/sda2 rootdelay=10
x_bootcmd_ethernet=ping 192.168.2.1
x_bootcmd_kernel=fatload usb 0 0x6400000 uImage
x_bootcmd_usb=usb start

Environment size: 553/4092 bytes
Marvell>>
Marvell>> bdinfo
arch_number = 0x00000DDE
boot_params = 0x00000100
DRAM bank   = 0x00000000
-> start    = 0x00000000
-> size     = 0x10000000
DRAM bank   = 0x00000001
-> start    = 0x10000000
-> size     = 0x10000000
ethaddr     = F0:AD:4E:00:7E:FB
ip_addr     = 0.0.0.0
baudrate    = 115200 bps
TLB addr    = 0x1FFF0000
relocaddr   = 0x1FF7F000
reloc off   = 0x1F97F000
irq_sp      = 0x1FE7DF68
sp start    = 0x1FE7DF58
FB base     = 0x00000000
Marvell>>
« Last Edit: 02 December 2013, 01:09:20 pm by DS »
Logged

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: Dreambrick... Uboot environment flash???
« Reply #1 on: 01 December 2013, 08:37:53 am »

You say it 'fails to boot' - what actually comes up via the Jtag?
Logged

DS

  • Newbie
  • *
  • Posts: 4
Re: Dreambrick... Uboot environment flash???
« Reply #2 on: 01 December 2013, 09:23:57 am »

Nothing.

I can get it to start the u-boot environment using kwuartboot and then write u-boot.kwb to flash, but as soon as you restart the device it doesn't do anything. The console screen via jtag doesn't show anything and the power light stays green.
Logged

Ralph Houston

  • New IT customer
  • Full Member
  • *
  • Posts: 136
Re: Dreambrick... Uboot environment flash???
« Reply #3 on: 01 December 2013, 05:57:31 pm »

Nothing you say.
How did you get the printenv then - did you hit a key to stop the boot, or was this from prior to the flash?
What made you decide to mess with the uboot anyway?
What happens if you type 'boot'?
What are you expecting to boot?
The Debians, Ubuntus etc. give the blue disco, but guiplug doesn't switch on any other LEDs, and requires a monitor that returns an ID before it displays to that.
I use minicom and find I have to connect everything from cold, start minicom and then the DP, otherwise the jtag ends up as ttyusb1 and the DP OS booting messages fail to appear.
Logged

DS

  • Newbie
  • *
  • Posts: 4
Re: Dreambrick... Uboot environment flash???
« Reply #4 on: 01 December 2013, 06:26:19 pm »

I am able to get it to run a uboot environment using kwuartboot and the u-boot.kwb that was supplied with the program, it's a similar method to using openocd but without all the hassle that comes with using openocd. I was trying to update uboot to a version that supports ext file format.

I found the link to kwuartboot in another thread on the forum.
https://newit.co.uk/forum/index.php/topic,3521.msg10254.html#msg10254
http://www.solinno.co.uk/public/kwuartboot/
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 663
Re: Dreambrick... Uboot environment flash???
« Reply #5 on: 01 December 2013, 09:15:13 pm »

You require two *different* u-boot images, one which runs from RAM which you load with kwuartboot, and the other that runs from flash that you transfer and burn with the kwuartboot loaded version of u-boot.
I suggest you follow the guides on this forum.
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

DS

  • Newbie
  • *
  • Posts: 4
Re: Dreambrick... Uboot environment flash???
« Reply #6 on: 02 December 2013, 01:08:38 pm »

You require two *different* u-boot images, one which runs from RAM which you load with kwuartboot, and the other that runs from flash that you transfer and burn with the kwuartboot loaded version of u-boot.

Thanks for the help. I've got it running by writing the u-boot.kwb file to flash that I extracted from the u-boot_2013.10-3_armel.deb package that I downloaded from the link bellow.
http://packages.debian.org/sid/armel/u-boot/download
Logged
Pages: [1]
 
 

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