Anyone got Wheezy running on a Dreamplug?

classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Anyone got Wheezy running on a Dreamplug?

Tixy-2
Does anyone know of any foolproof method of getting Wheezy running on a
Dreamplug?

I believe this requires upgrading U-Boot (to get device-tree support/fix
L2 cache issue?) but when I tried upgrading U-Boot by flashing it from
U-Boot I ended up with an expensive brick. Now this may have been user
error, but I don't want to risk bricking the new DreamPlug I bought
without instructions which are known to work. Or, perhaps the safest
thing is to load a new U-Boot from the old one if that's possible? And
in desperation I may even resort to writing a shim to make the Wheezy
kernel load with the stock U-Boot.

The method I was following which created a brick was to use the U-Boot
binary linked from Martin Michlmayr's page [1] and flash it using the
the sf probe/erase/write commands from the FreedomBox site [2].

My attempts to debrick using openocd and the JTAG module were the same
as another user [3] even when I scripted power cycling and openocd to
run in a loop a to try and get the timing right (which was one of the
suggested remedies). I gave up after 1000's of cycles in a overnight
run.

I then found kwuartboot [4] and thought I was saved, however both my old
and new DreamPlugs die after the first xmodem packet is sent. I verified
that the boot ROM is version 1.21 by sending the debug pattern to the
boards and seeing the response. After sending the boot pattern I see
byte 0x15 being sent from the plug every second on the serial port,
which is the correct behaviour for waiting for an xmodem. However after
sending the first xmodem packet the board don't send an ACK, and any
further packet retries result in the packet being echoed back.

I've tried sending different U-Boot files as well (e.g. the one in the
Debian U-Boot package). And just in case I have a new incompatible
DreamPlug variant I compared the kwbimage header from the NOR of my new
stock plug with those in the images I was trying to load via UART; the
header contents are the same apart from the length and CRC fields as we
would expect.

So that lead me to this plea for help :-)

[1] http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/
[2] http://freedomboxfoundation.org/ubootUpgradeInstructions/index.en.html
[3] http://www.newit.co.uk/forum/index.php?PHPSESSID=qqriddgo7r3fqce3pj1f08f5t7&topic=2619.0
[4] http://www.solinno.co.uk/public/kwuartboot/

--
Tixy


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368779043.3270.39.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Ian Campbell-2
Hi Tixy,

On Fri, 2013-05-17 at 09:24 +0100, Tixy wrote:

> Does anyone know of any foolproof method of getting Wheezy running on a
> Dreamplug?
>
> I believe this requires upgrading U-Boot (to get device-tree support/fix
> L2 cache issue?) but when I tried upgrading U-Boot by flashing it from
> U-Boot I ended up with an expensive brick. Now this may have been user
> error, but I don't want to risk bricking the new DreamPlug I bought
> without instructions which are known to work. Or, perhaps the safest
> thing is to load a new U-Boot from the old one if that's possible? And
> in desperation I may even resort to writing a shim to make the Wheezy
> kernel load with the stock U-Boot.
You can do this with devio. My NOTES file says (I've not tried this
recently, but I'm reasonably sure it worked when I made the notes):
        $ (
                # disable l2 caches
                devio "wl 0xee3f3f11,4" # mrc     15, 1, r3, cr15, cr1, {0}
                devio "wl 0xe3c33501,4" # bic     r3, r3, #4194304        ; 0x400000
                devio "wl 0xee2f3f11,4" # mcr     15, 1, r3, cr15, cr1, {0}
       
                # flush caches
                devio "wl 0xe3a03000,4" # mov     r3, #0
                devio "wl 0xee073f17,4" # mcr     15, 0, r3, cr7, cr7, {0}
       
                cat vmlinuz-3.2.0-3-kirkwood
        )> vmlinuz.devio
        $ mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 \
        -n "kernel 3.2.0-3-kirkwood" -d vmlinuz.devio myuImage

This ought to work equally well with the kernel file provided by the
installer.

> The method I was following which created a brick was to use the U-Boot
> binary linked from Martin Michlmayr's page [1] and flash it using the
> the sf probe/erase/write commands from the FreedomBox site [2].

FWIW what works for me is:
        Marvell>> tftp 0x6400000 u-boot.kwb
        Marvell>> sf probe 0
        Marvell>> sf erase 0x0 0x100000
        Marvell>> sf write 0x6400000 0x0 0x${filesize}

or if you have the u-boot package installed:
        Marvell>> usb start
        Marvell>> ext2load usb 1:2 0x6400000 /usr/lib/u-boot/dreamplug/u-boot.kwb
        Marvell>> sf probe 0
        Marvell>> sf erase 0x0 0x80000
        Marvell>> sf write 0x6400000 0x0 0x${filesize}  

> My attempts to debrick using openocd and the JTAG module were the same
> as another user [3] even when I scripted power cycling and openocd to
> run in a loop a to try and get the timing right (which was one of the
> suggested remedies). I gave up after 1000's of cycles in a overnight
> run.

It does seem to be a bit of a dice roll if it works. FWIW I use:
        sudo openocd -f /usr/share/openocd/scripts/board/sheevaplug.cfg -s /usr/share/openocd/scripts
Then telnet to localhost port 4444 and:
        reset;sheevaplug_init;load_image [path]/u-boot;resume 0x00600000

The openocd version is the Debian package 0.5.0-1, running on amd64.

Sadly based on that forum thread I don't expect that will help you.

I do remember having problems with loose cables between the DP and the
UART/JTAG module early on, but a firm reseating helped there.

Ian.

signature.asc (853 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Tixy-2
On Sat, 2013-05-18 at 11:40 +0100, Ian Campbell wrote:

> Hi Tixy,
>
> On Fri, 2013-05-17 at 09:24 +0100, Tixy wrote:
> > Does anyone know of any foolproof method of getting Wheezy running on a
> > Dreamplug?
> >
> > I believe this requires upgrading U-Boot (to get device-tree support/fix
> > L2 cache issue?) but when I tried upgrading U-Boot by flashing it from
> > U-Boot I ended up with an expensive brick. Now this may have been user
> > error, but I don't want to risk bricking the new DreamPlug I bought
> > without instructions which are known to work. Or, perhaps the safest
> > thing is to load a new U-Boot from the old one if that's possible? And
> > in desperation I may even resort to writing a shim to make the Wheezy
> > kernel load with the stock U-Boot.
>
> You can do this with devio. My NOTES file says (I've not tried this
> recently, but I'm reasonably sure it worked when I made the notes):
>         $ (
>                 # disable l2 caches
>                 devio "wl 0xee3f3f11,4" # mrc     15, 1, r3, cr15, cr1, {0}
>                 devio "wl 0xe3c33501,4" # bic     r3, r3, #4194304        ; 0x400000
>                 devio "wl 0xee2f3f11,4" # mcr     15, 1, r3, cr15, cr1, {0}
>        
>                 # flush caches
>                 devio "wl 0xe3a03000,4" # mov     r3, #0
>                 devio "wl 0xee073f17,4" # mcr     15, 0, r3, cr7, cr7, {0}
>        
>                 cat vmlinuz-3.2.0-3-kirkwood
>         )> vmlinuz.devio
>         $ mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 \
>         -n "kernel 3.2.0-3-kirkwood" -d vmlinuz.devio myuImage
>
> This ought to work equally well with the kernel file provided by the
> installer.

If does if you append the device-tree to the kernel as well. I ended up
trying to extend the devio shim for device-tree and was having problems,
then saw the Debian Kirkwood image has CONFIG_ARM_APPENDED_DTB :-)

So for others finding this thread, I ended up with this method to
convert the installer uImage into one which will boot on the DreamPlug
with the stock U-Boot which ships on the DreamPlug...

        (
        # disable l2 caches
        devio "wl 0xee3f3f11,4" # mrc     15, 1, r3, cr15, cr1, {0}
        devio "wl 0xe3c33501,4" # bic     r3, r3, #4194304        ; 0x400000
        devio "wl 0xee2f3f11,4" # mcr     15, 1, r3, cr15, cr1, {0}
       
        # flush caches
        devio "wl 0xe3a03000,4" # mov     r3, #0
        devio "wl 0xee073f17,4" # mcr     15, 0, r3, cr7, cr7, {0}
       
        # remove uboot header from the uImage we want to boot
        dd if=original-uImage bs=1 skip=64
        # append dtb to kernel image
        cat kirkwood-dreamplug.dtb          
        )> vmlinuz.devio
       
        mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 \
                        -n "kernel 3.2.0-4-kirkwood" -d vmlinuz.devio new-uImage

I got the dtb file from linux-image-3.2.0-4-kirkwood_3.2.41-2_armel.deb

Of course, I will need to do similar processing of the image the
installer puts in the boot partition, and repeat each time we get a
kernel update.

Thanks Ian for your help.

--
Tixy




--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368900026.3277.25.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Michael Howard
In reply to this post by Tixy-2
On 17/05/2013 09:24, Tixy wrote:
Apologies, originally sent direct to Tixy by mistake. Oh, the misteaks
we meet!
> Does anyone know of any foolproof method of getting Wheezy running on a
> Dreamplug?

I'm running Wheezy on all my DPs.

>
> I believe this requires upgrading U-Boot (to get device-tree support/fix
> L2 cache issue?) but when I tried upgrading U-Boot by flashing it from
> U-Boot I ended up with an expensive brick. Now this may have been user
> error, but I don't want to risk bricking the new DreamPlug I bought
> without instructions which are known to work. Or, perhaps the safest
> thing is to load a new U-Boot from the old one if that's possible? And
> in desperation I may even resort to writing a shim to make the Wheezy
> kernel load with the stock U-Boot.

u-boot update process I've used on both older and newer versions of the
DP is as follows;

# Following 3 steps can be done on or off the DP
# Modify to suit the u-boot you require
wget http://<fav
mirror>/debian/pool/main/u/u-boot/u-boot_2013.01.01-3_armel.deb

# Modify dest dir as you like
dpkg-deb -x u-boot_2013.01.01-3_armel.deb u-boot_2013.01.01-3_armel

#  /mnt here is on any media that you will have access to when booting
the DP
cp -r u-boot_2013.01.01-3_armel/usr/lib/u-boot/dreamplug /mnt

# On the DP
usb start
# Modify to ext2load if req and modify dev:part as req
fatload usb 0:3 0x6400000 dreamplug/u-boot.kwb
sf probe 0
sf erase 0x0 0x80000
# 0x3AB9C = size of u-boot.kwb
sf write 0x6400000 0x0 0x3AB9C

That's it. If it didn't work for you then possible user error? File size
error?

But you don't need to update u-boot specifically for Wheezy. You don't
need FDT support either.
If you have squeeze you could just upgrade.

Or am I missing something?

--


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/5197EDA8.3060809@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Tixy-2
On Sat, 2013-05-18 at 22:07 +0100, Mike Howard wrote:

> u-boot update process I've used on both older and newer versions of the
> DP is as follows;
>
> # Following 3 steps can be done on or off the DP
> # Modify to suit the u-boot you require
> wget http://<fav
> mirror>/debian/pool/main/u/u-boot/u-boot_2013.01.01-3_armel.deb
>
> # Modify dest dir as you like
> dpkg-deb -x u-boot_2013.01.01-3_armel.deb u-boot_2013.01.01-3_armel
>
> #  /mnt here is on any media that you will have access to when booting
> the DP
> cp -r u-boot_2013.01.01-3_armel/usr/lib/u-boot/dreamplug /mnt
>
> # On the DP
> usb start
> # Modify to ext2load if req and modify dev:part as req
> fatload usb 0:3 0x6400000 dreamplug/u-boot.kwb
> sf probe 0
> sf erase 0x0 0x80000
> # 0x3AB9C = size of u-boot.kwb
> sf write 0x6400000 0x0 0x3AB9C
>
> That's it. If it didn't work for you then possible user error? File size
> error?

Possible/probable user error, but as I've already bricked one DreamPlug
and had to buy a replacement I'm very reluctant to give it another go.

>
> But you don't need to update u-boot specifically for Wheezy. You don't
> need FDT support either.
> If you have squeeze you could just upgrade.
>
> Or am I missing something?

I wanted to run the stock Debian kernel, that requires a fixed U-Boot or
to add a shim to flush the L2 cache like Ian Campbell showed. I also
want to do a fresh install with my own choice of packages and config
rather than upgrade what the plug ships with.

Installing is no problem, I've done it dozens of times on various
machines, I was just struggling with getting the kernel booting.

Also, a U-Boot that supports FDT would be required should I want to run
Testing which will have the multi-platform kernel. Unless they are going
to build that with CONFIG_ARM_APPENDED_DTB, which I hope they don't as
that's a hack and isn't completely robust (I believe) for people who
don't append an FDT.

--
Tixy



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368951867.3276.17.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Ian Campbell-2
In reply to this post by Tixy-2
On Sat, 2013-05-18 at 19:00 +0100, Tixy wrote:

> On Sat, 2013-05-18 at 11:40 +0100, Ian Campbell wrote:
> > Hi Tixy,
> >
> > On Fri, 2013-05-17 at 09:24 +0100, Tixy wrote:
> > > Does anyone know of any foolproof method of getting Wheezy running on a
> > > Dreamplug?
> > >
> > > I believe this requires upgrading U-Boot (to get device-tree support/fix
> > > L2 cache issue?) but when I tried upgrading U-Boot by flashing it from
> > > U-Boot I ended up with an expensive brick. Now this may have been user
> > > error, but I don't want to risk bricking the new DreamPlug I bought
> > > without instructions which are known to work. Or, perhaps the safest
> > > thing is to load a new U-Boot from the old one if that's possible? And
> > > in desperation I may even resort to writing a shim to make the Wheezy
> > > kernel load with the stock U-Boot.
> >
> > You can do this with devio. My NOTES file says (I've not tried this
> > recently, but I'm reasonably sure it worked when I made the notes):
> >         $ (
> >                 # disable l2 caches
> >                 devio "wl 0xee3f3f11,4" # mrc     15, 1, r3, cr15, cr1, {0}
> >                 devio "wl 0xe3c33501,4" # bic     r3, r3, #4194304        ; 0x400000
> >                 devio "wl 0xee2f3f11,4" # mcr     15, 1, r3, cr15, cr1, {0}
> >        
> >                 # flush caches
> >                 devio "wl 0xe3a03000,4" # mov     r3, #0
> >                 devio "wl 0xee073f17,4" # mcr     15, 0, r3, cr7, cr7, {0}
> >        
> >                 cat vmlinuz-3.2.0-3-kirkwood
> >         )> vmlinuz.devio
> >         $ mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 \
> >         -n "kernel 3.2.0-3-kirkwood" -d vmlinuz.devio myuImage
> >
> > This ought to work equally well with the kernel file provided by the
> > installer.
>
> If does if you append the device-tree to the kernel as well. I ended up
> trying to extend the devio shim for device-tree and was having problems,
> then saw the Debian Kirkwood image has CONFIG_ARM_APPENDED_DTB :-)
>
> So for others finding this thread, I ended up with this method to
> convert the installer uImage into one which will boot on the DreamPlug
> with the stock U-Boot which ships on the DreamPlug...
>
>         (
>         # disable l2 caches
>         devio "wl 0xee3f3f11,4" # mrc     15, 1, r3, cr15, cr1, {0}
>         devio "wl 0xe3c33501,4" # bic     r3, r3, #4194304        ; 0x400000
>         devio "wl 0xee2f3f11,4" # mcr     15, 1, r3, cr15, cr1, {0}
>        
>         # flush caches
>         devio "wl 0xe3a03000,4" # mov     r3, #0
>         devio "wl 0xee073f17,4" # mcr     15, 0, r3, cr7, cr7, {0}
>        
>         # remove uboot header from the uImage we want to boot
>         dd if=original-uImage bs=1 skip=64
>         # append dtb to kernel image
>         cat kirkwood-dreamplug.dtb          
>         )> vmlinuz.devio
>        
>         mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 \
>                         -n "kernel 3.2.0-4-kirkwood" -d vmlinuz.devio new-uImage
>
> I got the dtb file from linux-image-3.2.0-4-kirkwood_3.2.41-2_armel.deb

You may have (harmlessly) ended up appending the DTB twice since I think
the installer uImage has it already there...

> Of course, I will need to do similar processing of the image the
> installer puts in the boot partition, and repeat each time we get a
> kernel update.

Yes. Originally I thought the presence of JTAG was sufficient for us to
say "just update u-boot" to users, but it's become clear recently that
this option is not terribly reliable, so perhaps it would be wise to
teach the flash-kernel tool about this errata.

On the other hand, non-functioning JTAG seems like a good enough reason
to me to return a dreamplug to the manufacturer for a refund, especially
if you bought their JTAG module as well..

> Thanks Ian for your help.

My pleasure.

Ian.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368963225.12438.39.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Ian Campbell-2
In reply to this post by Tixy-2
On Sun, 2013-05-19 at 09:24 +0100, Tixy wrote:
> Also, a U-Boot that supports FDT would be required should I want to run
> Testing which will have the multi-platform kernel. Unless they are going
> to build that with CONFIG_ARM_APPENDED_DTB, which I hope they don't as
> that's a hack and isn't completely robust (I believe) for people who
> don't append an FDT.

AIUI the mp kernel flavour is for armhf (armv7) only, whereas the
dreamplug is armel (v5). I don't know about APPENDED_DTB on armhf. I
suppose armv7 platforms are much more likely to support fdt in their
u-boot.

The main danger with CONFIG_ARM_APPENDED_DTB is that there might, by
coincidence, happen to be something which looks like a DTB in the memory
right after where the kernel is. If for some reason we find ourselves
compelled to enable that option then teaching bootloaders to zero a few
bytes after the kernel is one option, as is teaching e.g. flash-kernel
to append a few zeroes to the image.

It also seems like it ought to be possible to replace any use of
CONFIG_ARM_APPENDED_DTB with a devio shim. I think that sounds
preferable since it confines the pain to the platforms with the
shortcomings...

Ian.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368963465.12438.43.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Tixy-2
In reply to this post by Ian Campbell-2
On Sun, 2013-05-19 at 12:33 +0100, Ian Campbell wrote:

> On Sat, 2013-05-18 at 19:00 +0100, Tixy wrote:
> > On Sat, 2013-05-18 at 11:40 +0100, Ian Campbell wrote:
> > > Hi Tixy,
> > >
> > > On Fri, 2013-05-17 at 09:24 +0100, Tixy wrote:
> > > > Does anyone know of any foolproof method of getting Wheezy running on a
> > > > Dreamplug?
> > > >
> > > > I believe this requires upgrading U-Boot (to get device-tree support/fix
> > > > L2 cache issue?) but when I tried upgrading U-Boot by flashing it from
> > > > U-Boot I ended up with an expensive brick. Now this may have been user
> > > > error, but I don't want to risk bricking the new DreamPlug I bought
> > > > without instructions which are known to work. Or, perhaps the safest
> > > > thing is to load a new U-Boot from the old one if that's possible? And
> > > > in desperation I may even resort to writing a shim to make the Wheezy
> > > > kernel load with the stock U-Boot.
> > >
> > > You can do this with devio. My NOTES file says (I've not tried this
> > > recently, but I'm reasonably sure it worked when I made the notes):
> > >         $ (
> > >                 # disable l2 caches
> > >                 devio "wl 0xee3f3f11,4" # mrc     15, 1, r3, cr15, cr1, {0}
> > >                 devio "wl 0xe3c33501,4" # bic     r3, r3, #4194304        ; 0x400000
> > >                 devio "wl 0xee2f3f11,4" # mcr     15, 1, r3, cr15, cr1, {0}
> > >        
> > >                 # flush caches
> > >                 devio "wl 0xe3a03000,4" # mov     r3, #0
> > >                 devio "wl 0xee073f17,4" # mcr     15, 0, r3, cr7, cr7, {0}
> > >        
> > >                 cat vmlinuz-3.2.0-3-kirkwood
> > >         )> vmlinuz.devio
> > >         $ mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 \
> > >         -n "kernel 3.2.0-3-kirkwood" -d vmlinuz.devio myuImage
> > >
> > > This ought to work equally well with the kernel file provided by the
> > > installer.
> >
> > If does if you append the device-tree to the kernel as well. I ended up
> > trying to extend the devio shim for device-tree and was having problems,
> > then saw the Debian Kirkwood image has CONFIG_ARM_APPENDED_DTB :-)
> >
> > So for others finding this thread, I ended up with this method to
> > convert the installer uImage into one which will boot on the DreamPlug
> > with the stock U-Boot which ships on the DreamPlug...
> >
> >         (
> >         # disable l2 caches
> >         devio "wl 0xee3f3f11,4" # mrc     15, 1, r3, cr15, cr1, {0}
> >         devio "wl 0xe3c33501,4" # bic     r3, r3, #4194304        ; 0x400000
> >         devio "wl 0xee2f3f11,4" # mcr     15, 1, r3, cr15, cr1, {0}
> >        
> >         # flush caches
> >         devio "wl 0xe3a03000,4" # mov     r3, #0
> >         devio "wl 0xee073f17,4" # mcr     15, 0, r3, cr7, cr7, {0}
> >        
> >         # remove uboot header from the uImage we want to boot
> >         dd if=original-uImage bs=1 skip=64
> >         # append dtb to kernel image
> >         cat kirkwood-dreamplug.dtb          
> >         )> vmlinuz.devio
> >        
> >         mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 \
> >                         -n "kernel 3.2.0-4-kirkwood" -d vmlinuz.devio new-uImage
> >
> > I got the dtb file from linux-image-3.2.0-4-kirkwood_3.2.41-2_armel.deb
>
> You may have (harmlessly) ended up appending the DTB twice since I think
> the installer uImage has it already there...

It doesn't, I just checked, and if it did have the DreamPlug dtb it
wouldn't work on the iconnect which also has a dtb in the kirkwood
kernel package and so I assume is also supported.

--
Tixu


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368970873.4213.8.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Ian Campbell-2
On Sun, 2013-05-19 at 14:41 +0100, Tixy wrote:
> On Sun, 2013-05-19 at 12:33 +0100, Ian Campbell wrote:

> > You may have (harmlessly) ended up appending the DTB twice since I think
> > the installer uImage has it already there...
>
> It doesn't, I just checked, and if it did have the DreamPlug dtb it
> wouldn't work on the iconnect which also has a dtb in the kirkwood
> kernel package and so I assume is also supported.

Which kernel were you using?

ftp://ftp.uk.debian.org/debian/dists/wheezy/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/ should have the device tree appended. From the Debian Installer source:
        dreamplug: sheevaplug
                mkdir -p $(SOME_DEST)/$(EXTRANAME)/marvell/dreamplug
                cat $(TEMP_KERNEL) $(TEMP_DTB)/kirkwood-dreamplug.dtb > $(TEMP)/vmlinuz-dreamplug
                mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n "Debian kernel" -d $(TEMP)/vmlinuz-dreamplug $(SOME_DEST)/$(EXTRANAME)/marvell/dreamplug/uImage
        ...snip

The sheevaplug one doesn't have that.

The iconnect doesn't appear to have a specific d-i image. Perhaps its
u-boot does fdt already.

Ian.



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368972732.24012.70.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Michael Howard
In reply to this post by Tixy-2
On 19/05/2013 09:24, Tixy wrote:

> On Sat, 2013-05-18 at 22:07 +0100, Mike Howard wrote:
>
>> u-boot update process I've used on both older and newer versions of the
>> DP is as follows;
>>
>> # Following 3 steps can be done on or off the DP
>> # Modify to suit the u-boot you require
>> wget http://<fav
>> mirror>/debian/pool/main/u/u-boot/u-boot_2013.01.01-3_armel.deb
>>
>> # Modify dest dir as you like
>> dpkg-deb -x u-boot_2013.01.01-3_armel.deb u-boot_2013.01.01-3_armel
>>
>> #  /mnt here is on any media that you will have access to when booting
>> the DP
>> cp -r u-boot_2013.01.01-3_armel/usr/lib/u-boot/dreamplug /mnt
>>
>> # On the DP
>> usb start
>> # Modify to ext2load if req and modify dev:part as req
>> fatload usb 0:3 0x6400000 dreamplug/u-boot.kwb
>> sf probe 0
>> sf erase 0x0 0x80000
>> # 0x3AB9C = size of u-boot.kwb
>> sf write 0x6400000 0x0 0x3AB9C
>>
>> That's it. If it didn't work for you then possible user error? File size
>> error?
> Possible/probable user error, but as I've already bricked one DreamPlug
> and had to buy a replacement I'm very reluctant to give it another go.
>
>> But you don't need to update u-boot specifically for Wheezy. You don't
>> need FDT support either.
>> If you have squeeze you could just upgrade.
>>
>> Or am I missing something?
> I wanted to run the stock Debian kernel, that requires a fixed U-Boot or
> to add a shim to flush the L2 cache like Ian Campbell showed. I also
> want to do a fresh install with my own choice of packages and config
> rather than upgrade what the plug ships with.

Ok, then the u-boot install procedure above has always worked for me,
followed by a fresh install using the Wheezy installer.


--


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/5198F103.5000203@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Tixy-2
In reply to this post by Ian Campbell-2
On Sun, 2013-05-19 at 15:12 +0100, Ian Campbell wrote:

> On Sun, 2013-05-19 at 14:41 +0100, Tixy wrote:
> > On Sun, 2013-05-19 at 12:33 +0100, Ian Campbell wrote:
>
> > > You may have (harmlessly) ended up appending the DTB twice since I think
> > > the installer uImage has it already there...
> >
> > It doesn't, I just checked, and if it did have the DreamPlug dtb it
> > wouldn't work on the iconnect which also has a dtb in the kirkwood
> > kernel package and so I assume is also supported.
>
> Which kernel were you using?

I was using the one linked to from
http://www.cyrius.com/debian/kirkwood/sheevaplug/install/
which I now see is the SheevaPlug one.

> ftp://ftp.uk.debian.org/debian/dists/wheezy/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/ should have the device tree appended.

Yes, it does.

Seems that Martin Michlmayr's otherwise excellent pages have just had
the DreamPlug added to the list of supported devices without any
indication that you need a different uImage and that the process for
updating U-Boot is different.

Sitting here looking at the DreamPlug with it's ugly and fragile module
taped to it so I've got a serial port, and cut'n'pasting commands 8
characters at a time because said serial doesn't have hardware flow
control and will drop character otherwise, I can't help but suspect that
the plug is going to get put pack in the cupboard and not see the light
of day again.

Now if only I had bought a couple of OpenRD Ultimates when they were
available. The certainly look the business.

--
Tixy


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368977858.3441.32.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Michael Howard
On 19/05/2013 16:37, Tixy wrote:

> On Sun, 2013-05-19 at 15:12 +0100, Ian Campbell wrote:
>> On Sun, 2013-05-19 at 14:41 +0100, Tixy wrote:
>>> On Sun, 2013-05-19 at 12:33 +0100, Ian Campbell wrote:
>>>> You may have (harmlessly) ended up appending the DTB twice since I think
>>>> the installer uImage has it already there...
>>> It doesn't, I just checked, and if it did have the DreamPlug dtb it
>>> wouldn't work on the iconnect which also has a dtb in the kirkwood
>>> kernel package and so I assume is also supported.
>> Which kernel were you using?
> I was using the one linked to from
> http://www.cyrius.com/debian/kirkwood/sheevaplug/install/
> which I now see is the SheevaPlug one.
>
>> ftp://ftp.uk.debian.org/debian/dists/wheezy/main/installer-armel/current/images/kirkwood/netboot/marvell/dreamplug/ should have the device tree appended.
> Yes, it does.
>
> Seems that Martin Michlmayr's otherwise excellent pages have just had
> the DreamPlug added to the list of supported devices without any
> indication that you need a different uImage and that the process for
> updating U-Boot is different.
>
> Sitting here looking at the DreamPlug with it's ugly and fragile module
> taped to it so I've got a serial port, and cut'n'pasting commands 8
> characters at a time because said serial doesn't have hardware flow
> control and will drop character otherwise, I can't help but suspect that
> the plug is going to get put pack in the cupboard and not see the light
> of day again.
>
> Now if only I had bought a couple of OpenRD Ultimates when they were
> available. The certainly look the business.
>
Well if you don't want it, I'll gladly take it off your hands.

--


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/5198FA35.6040909@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Tixy-2
In reply to this post by Ian Campbell-2
On Sat, 2013-05-18 at 11:40 +0100, Ian Campbell wrote:

> On Fri, 2013-05-17 at 09:24 +0100, Tixy wrote:

> > My attempts to debrick using openocd and the JTAG module were the same
> > as another user [3] even when I scripted power cycling and openocd to
> > run in a loop a to try and get the timing right (which was one of the
> > suggested remedies). I gave up after 1000's of cycles in a overnight
> > run.
>
> It does seem to be a bit of a dice roll if it works. FWIW I use:
>         sudo openocd -f /usr/share/openocd/scripts/board/sheevaplug.cfg -s /usr/share/openocd/scripts
> Then telnet to localhost port 4444 and:
>         reset;sheevaplug_init;load_image [path]/u-boot;resume 0x00600000
>
> The openocd version is the Debian package 0.5.0-1, running on amd64.
>
> Sadly based on that forum thread I don't expect that will help you.
>
> I do remember having problems with loose cables between the DP and the
> UART/JTAG module early on, but a firm reseating helped there.

Well, what do you know... I thought I'd give this one last try, I took
my bricked plug out of its case, to get better access, rammed the
connectors home, then tried JTAG connection whilst pulling the cables in
different directions and after about 10 tries got a U-Boot loaded into
RAM :-) And I've successfully loaded and flashed the Debian U-Boot using
the instructions that everyone says works.

Now all I need to do is get my soldering iron out. The separate SD card
board in the box had connectors which are glue in so I cut the cables,
thinking it was only for the internal micro SD (which I don't need) and
not realising it's needed for the external SD card as well. DOH!

--
Tixy


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368985793.6618.13.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Tixy-2
In reply to this post by Michael Howard
On Sun, 2013-05-19 at 17:13 +0100, Mike Howard wrote:

> Well if you don't want it, I'll gladly take it off your hands.

You very near did get them, but having managed to finally de-brick my
original DreamPlug I think I'll persevere with them.

Perhaps I can create new boxes for them and mount the JTAG/UART module
internally...

--
Tixy



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1368986378.6618.19.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Michael Howard
On 19/05/2013 18:59, Tixy wrote:
> On Sun, 2013-05-19 at 17:13 +0100, Mike Howard wrote:
>
>> Well if you don't want it, I'll gladly take it off your hands.
> You very near did get them, but having managed to finally de-brick my
> original DreamPlug I think I'll persevere with them.
>
> Perhaps I can create new boxes for them and mount the JTAG/UART module
> internally...
>

Glad you got success.

As an aside, I have a couple of guruplug servers in clear plastic lunch
boxes ..........

--


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/519931D7.5030700@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Ian Campbell-2
In reply to this post by Tixy-2
On Sun, 2013-05-19 at 18:49 +0100, Tixy wrote:

> On Sat, 2013-05-18 at 11:40 +0100, Ian Campbell wrote:
> > I do remember having problems with loose cables between the DP and the
> > UART/JTAG module early on, but a firm reseating helped there.
>
> Well, what do you know... I thought I'd give this one last try, I took
> my bricked plug out of its case, to get better access, rammed the
> connectors home, then tried JTAG connection whilst pulling the cables in
> different directions and after about 10 tries got a U-Boot loaded into
> RAM :-) And I've successfully loaded and flashed the Debian U-Boot using
> the instructions that everyone says works.

Excellent, I always thought those bundle-o-wires things were a bit
dodgy looking...

> Now all I need to do is get my soldering iron out. The separate SD card
> board in the box had connectors which are glue in so I cut the cables,
> thinking it was only for the internal micro SD (which I don't need) and
> not realising it's needed for the external SD card as well. DOH!

Doh Indeed!

Ian.



--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1369043672.10868.2.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Martin Michlmayr
In reply to this post by Tixy-2
* Tixy <[hidden email]> [2013-05-19 16:37]:
> Seems that Martin Michlmayr's otherwise excellent pages have just had
> the DreamPlug added to the list of supported devices without any
> indication that you need a different uImage and that the process for
> updating U-Boot is different.

That's correct.  I donn't have a DreamPlug, so I wasn't aware that
other changes were required for the documentation.

Thanks to your feedback, I've now updated the instructions (see
attached patch).  If anything else is missing, please let me know.

--
Martin Michlmayr
http://www.cyrius.com/

dreamplug.patch (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Tixy-2
On Sun, 2013-06-16 at 10:48 +0100, Martin Michlmayr wrote:

> * Tixy <[hidden email]> [2013-05-19 16:37]:
> > Seems that Martin Michlmayr's otherwise excellent pages have just had
> > the DreamPlug added to the list of supported devices without any
> > indication that you need a different uImage and that the process for
> > updating U-Boot is different.
>
> That's correct.  I donn't have a DreamPlug, so I wasn't aware that
> other changes were required for the documentation.
>
> Thanks to your feedback, I've now updated the instructions (see
> attached patch).  If anything else is missing, please let me know.

Those changes look good to me. One thing though, the USB device numbers
for GuruPlug and DreamPlug will be different that zero, as zero would be
the internally fitted microSD. E.g. on a Dreamplug with the U-Boot from
Debian (think stock U-Boot was same) the external MMC card is device 1,
so we would need:

   fatload usb 1:1 ...

and a USB stick would require:

   fatload usb 2:1 ...

--
Tixy




--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/1371379596.3266.10.camel@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Martin Michlmayr
* Tixy <[hidden email]> [2013-06-16 11:46]:
> Those changes look good to me. One thing though, the USB device numbers
> for GuruPlug and DreamPlug will be different that zero, as zero would be
> the internally fitted microSD. E.g. on a Dreamplug with the U-Boot from
> Debian (think stock U-Boot was same) the external MMC card is device 1,
> so we would need:

Thanks, I added a note about this!

--
Martin Michlmayr
http://www.cyrius.com/


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]
Archive: http://lists.debian.org/20130625151325.GD27260@...

Reply | Threaded
Open this post in threaded view
|

Re: Anyone got Wheezy running on a Dreamplug?

Adam Ward-3
In reply to this post by Martin Michlmayr

I have a Dreamplug shipped from spinnifex in Australia.

The u-boot version is as follows:

 

Marvell>> version

 

U-Boot 2011.06-02334-g8f495d9-dirty (Aug 18 2011 - 02:09:07)

Marvell-DreamPlug

 

Is it safe to change to the DENX version given the instructions on Martin's site [1]

 

[1] http://cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/

 

12