SD Card Not Formatted for Recovery

Hi Wes,

 By using make sd_boot_recover dev=/dev/sde1 you're indicating partition 1 on your SD. Try using /dev/sde instead

Regards,

Pablo

Pablo,

BEAUTIFUL!  And now I also understand a little bit about device names I didn't know before.

The card wrote and turned my brick back into a working card. Many, many thanks!

Warmly,

Wesley

To Whomever Maintains the Online Documentation:

A couple of suggestions about the documentation in the DM365 Leopard SDK Getting Started Guide.

At the instructions for make bootloader and make install add some explicit instructions to open a minicom or putty session,  reboot the card and halt it in the uboot process at the "Press any key to ..." then to close the terminal program. 

I believe this will significantly reduce the number of "bricked" cards that have to be recovered.

Also, similar to the Leopardboard 355 instructions in Installing RR free SDK for Leopard Board some pictures and session logs would be very helpful, especially something to illustrate what we should expect to see if the card boots correctly.  I kept expecting to see the RidgeRun "asciii character" logo art.

RidgeRun

Welcome to
__________ .__     .___               __________               
\______   \|__|  __| _/  ____    ____ \______   \ __ __   ____ 
 |       _/|  | / __ |  / ___\ _/ __ \ |       _/|  |  \ /    \
 |    |   \|  |/ /_/ | / /_/  >\  ___/ |    |   \|  |  /|   |  \
 |____|_  /|__|\____ | \___  /  \___  >|____|_  /|____/ |___|  /
        \/          \//_____/       \/        \/             \/
          
    Embedded Linux Solutions

Thanks!

Wes

a

But Wait, There's More!

I just realized I had to repeat the make installbootloader and make install to actually transfer the RR SDK to my Leopardboard!  The recovery mechanism only puts something there that will get you back to square one.  It isn't the final product.  And there IS a RidgeRun logo, after all!

So, my kind keeper of the documents, could you add a line or two to the dos to say that?

One other fix I think is needed:  This paragraph confused me and several other people;

DM365 Leopard SDK Getting Started Guide

Notice the tarball contents are inside a folder named opt, DO NOT replace this folder with your local opt directory, just use its contents (arm-linux-gnueabi directory).

A replacement might read something like:

Notice, when the tarball is unpacked, it creates a folder named opt. Do not replace your /opt directory with this folder.  Instead, move its contents, a folder named  arm-linux-gnueabi, into your /opt directory.

From your download directory:

tar -jxvf toolchain.tar.bz2
cd opt
mv arm-linux-gnueabi /opt/.

Thanks!

Wes

Hi Wes,

I'm glad your problem was solved, also thanks for your advice, I'll edit the documentation properly.

Regards,

Pablo