The latest Stable Release of the RidgeRun SDK called 2011Q2 comes with a new installer system that give to the user a high flexibility and a huge variety of installation modes such as SD, NAND and JFFS2. However in order to achieve this features a new u-boot system must be placed in the board so it will support the features available.

+

The latest Stable Release of the RidgeRun SDK called Turrialba comes with a new installer system that give to the user a high flexibility and a huge variety of installation modes such as SD, NAND and JFFS2. However in order to achieve this features a new u-boot system must be placed in the board so it will support the features available.

Since a new board comes with the factory's default u-boot, it is necessary to flash the RidgeRun's u-boot in the board before continue using the SDK, but how can we install an image into the board using the RidgeRun's SDK if the board doesn't have the RidgeRun's u-boot installed?

Since a new board comes with the factory's default u-boot, it is necessary to flash the RidgeRun's u-boot in the board before continue using the SDK, but how can we install an image into the board using the RidgeRun's SDK if the board doesn't have the RidgeRun's u-boot installed?

−

Now we are going to explain how to flash the RidgeRun's SDK for the following boards:

+

Now we are going to explain how to flash the RidgeRun's u-boot for the following boards:

* LeopardBoard DM365

* LeopardBoard DM365

* TI DM365 EVM

* TI DM365 EVM

* OMAP35x TOBI

* OMAP35x TOBI

+

* Mistral DM37x EVM

= Flashing the u-boot into a LeopardBoard DM365 =

= Flashing the u-boot into a LeopardBoard DM365 =

+

+

In order to flash the RidgeRun's SDK into a LeopardBoard DM365 you need to follow the next steps:

You can create a SD card image following the steps listed in [[How to boot a board from a SD card]] or if you prefer you can download any of the pre-built SD card images available in [https://www.ridgerun.com/support/evaldm365leosdk/downloads/SD_images/ LeopardBoard DM365 pre-built images]. You need to be registered in order to get access into the link provided.

+

+

2. Once you have the image recorded into a SD card the next step is to boot the board from SD card as is also described in [[How to boot a board from a SD card]].

+

+

3. When the board is booting, stop it in the u-boot's count down as is shown below.

+

+

<pre>

+

U-Boot 2010.12-rc2 (Jun 20 2011 - 09:33:44)

+

+

Cores: ARM 297 MHz

+

DDR: 243 MHz

+

I2C: ready

+

DRAM: 128 MiB

+

NAND: 256 MiB

+

MMC: davinci: 0, davinci: 1

+

Net: Ethernet PHY: GENERIC @ 0x00

+

DaVinci-EMAC

+

Hit any key to stop autoboot: 0

+

DM365 LEOPARD #

+

</pre>

+

+

4. Exit from your minicom/termnet session.

+

+

5. Set the ''Attached board on communication port'' option in the configuration window (make config).

+

+

-> Installer Configuration

+

-> Firmware deployment mode (<choice> [=y])

+

-> Attached board on communication port

+

+

6. Build your SDK.

+

+

7. Once your SDK has been built, install the new bootloader into the board by running the following command:

+

+

<pre>

+

make installbootloader

+

</pre>

+

+

You will see a terminal output such as the shown below:

+

+

<pre>

+

$ make installbootloader

+

Ridgerun Linux SDK

+

Board configuration: Leopard Board DM365

+

Multi-core machine, using 3 out of 6 cores for building

+

+

Installation system of uboot images over TFTP for host 10.251.101.4

+

Be sure u-boot is running on 10.251.101.56:3001 and no process (like termnet) is using it

8. Once the process has finished turn off the board and turn off the dip switch 2 in the board so you will be able to boot from NAND using the new RidgeRun's u-boot.

= Flashing the u-boot into a TI DM365 EVM =

= Flashing the u-boot into a TI DM365 EVM =

−

= Flashing the u-boot into a OMAP35x TOBI =

+

In order to flash the RidgeRun's SDK into a DM365 EVM you need to follow the next steps:

+

+

1. Create or download a pre-built SD card image for EVM DM365.

+

+

You can create a SD card image following the steps listed in [[How to boot a board from a SD card]] or if you prefer you can download any of the pre-built SD card images available in [https://www.ridgerun.com/support/evaldm365evmsdk/downloads/SD_images/ DM365 EVM pre-built images]. You need to be registered in order to get access into the link provided.

+

+

2. Once you have the image recorded into a SD card the next step is to boot the board from SD card as is also described in [[How to boot a board from a SD card]].

+

+

3. When the board is booting, stop it in the u-boot's count down as is shown below.

+

+

<pre>

+

U-Boot 2010.12-rc2 (Jul 13 2011 - 14:13:31)

+

+

Cores: ARM 297 MHz

+

DDR: 243 MHz

+

I2C: ready

+

DRAM: 128 MiB

+

NAND: 2048 MiB

+

MMC: davinci: 0, davinci: 1

+

*** Warning - booting from SD, using default environment

+

+

Net: Ethernet PHY: GENERIC @ 0x00

+

DaVinci-EMAC

+

Hit any key to stop autoboot: 0

+

DM36x EVM #

+

</pre>

+

+

4. Exit from your minicom/termnet session.

+

+

5. Set the ''Attached board on communication port'' option in the configuration window (make config).

+

+

-> Installer Configuration

+

-> Firmware deployment mode (<choice> [=y])

+

-> Attached board on communication port

+

+

6. Build your SDK.

+

+

7. Once your SDK has been built, install the new bootloader into the board by running the following command:

+

+

<pre>

+

make installbootloader

+

</pre>

+

+

You will see a terminal output such as the shown below:

+

+

<pre>

+

$ make installbootloader

+

Ridgerun Linux SDK

+

Board configuration: DM365 Spectrum Digital EVM Board

+

Multi-core machine, using 4 out of 8 cores for building

+

+

Installation system of uboot images over TFTP for host 10.251.101.7

+

Be sure u-boot is running on 10.251.101.56:3001 and no process (like termnet) is using it

8. Once the process has finished turn off the board and turn off the switch 2 in the dip switch SW4 in the board so you will be able to boot from NAND using the new RidgeRun's u-boot.

+

+

= Flashing the u-boot into a Mistral Dm37x EVM =

+

+

In order to flash the RidgeRun's SDK into a Mistral Dm37x EVM you need to follow the next steps:

+

+

1. Create a SD card image for Mistral DM37x EVM.

+

+

You can create a SD card image following the steps listed in [[How to boot a board from a SD card]].

+

+

2. Once you have the image recorded into a SD card the next step is to boot the board from SD card using the correct switch configuration as is described in [[Mistral DM37x EVM SDK 2011Q2 Getting Started Guide]].

+

+

3. When the board is booting, stop it in the u-boot's count down as is shown below.

8. Once the process has finished restore the switch SW4 to NAND boot mode (see [[Mistral DM37x EVM SDK 2011Q2 Getting Started Guide]]) board so you will be able to boot from NAND using the new RidgeRun's u-boot.

+

+

= Flashing the u-boot into a DM81xx =

+

Please see section called Flashing uboot, kernel and filesystem in NAND in the [https://www.ridgerun.com/developer/wiki/index.php/Getting_Started_Guide_for_DM8168_EVM DM8168 support page]

Revision as of 10:58, 6 February 2013

Contents

Introduction

The latest Stable Release of the RidgeRun SDK called Turrialba comes with a new installer system that give to the user a high flexibility and a huge variety of installation modes such as SD, NAND and JFFS2. However in order to achieve this features a new u-boot system must be placed in the board so it will support the features available.

Since a new board comes with the factory's default u-boot, it is necessary to flash the RidgeRun's u-boot in the board before continue using the SDK, but how can we install an image into the board using the RidgeRun's SDK if the board doesn't have the RidgeRun's u-boot installed?

Now we are going to explain how to flash the RidgeRun's u-boot for the following boards:

LeopardBoard DM365

TI DM365 EVM

OMAP35x TOBI

Mistral DM37x EVM

Flashing the u-boot into a LeopardBoard DM365

In order to flash the RidgeRun's SDK into a LeopardBoard DM365 you need to follow the next steps: