How to reflash a boot loader and Linux image onto the Minimorph SPI flash

Tagged: ,

This topic contains 2 replies, has 2 voices, and was last updated by  Sean 4 years, 9 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #31083

    Sean
    Moderator

    You will need to have the Minimorph connected by USB to a Linux host.

    The SDK contains a binary application (hostboot) to enable updating of the SPI flash. Please see the following article regarding the versions available:
    http://forum.imgtec.com/discussion/2427

    Ensure you have extracted the correct hostboot and the flow_programmer.ldr or you have prepared your own.

    These instructions are also detailed in the Getting Started Guide documentation.


    Configure the Minimorph for USB slave boot
    1. Power off the board.

    2. Set the boot selection jumpers to ‘USB Slave Boot’ as follows:
    CN34 1
    CN33 1
    CN27 0

    3. Put the Boot/Debug switch (SW4) in the ‘Boot’ position.

    4. Connect the USB cable from your Linux host to the Minimorph.

    5. Press the Minimorph reset button (SW6).

    Reflash the Minimorph SPI flash using hostboot
    The hostboot binary file resides in the IMG directory, created when you unpacked the hostboot tar file.

    1. Run the hostboot binary, for example:
    $ ./hostboot IMG/flow_programmer.ldr
    The reflash will take several minutes. Hostboot completes and exits on the host PC before the reflash is complete.
    When it is complete soft LEDs 1 & 2 will flash alternately.
    Warning: Do not power off or unplug the board until you see the LEDs flashing.

    2. Set the boot selection jumpers to ‘Atmel Flash’ as follows:
    CN34 0
    CN33 0
    CN27 1

    3. Press the Minimorph reset button (SW6).

    The board will now reset, loading U-Boot from the SPI Flash then loading the Meta Linux kernel from SPI flash.
    When it is complete soft LED 2 will flash every 5 seconds to indicate the Minimorph has booted and is ready.

    #36417

    bmarshall
    Member

    I follow the process above to the letter. However upon running hostboot I get the following output:
    [root@localhost IMG]# ./hostboot ../flow_programmer.ldr
    beginning boot
    loading secload to 0xe02a0000
    extending boot ROM (secload entry 0xe0540000)
    loading data stream
    Response with incorrect header magic 0x0000
    Boot failed
    [root@localhost IMG]#

    I am running CENTOS 6.0 (using the correct version of hostboot) in a virtual machine on a windows host. The USB device is passed straight into the virtual machine.
    Any ideas?

    EDIT

    Oh, and the output of lsub is

    [root@localhost IMG]# lsusb
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 005: ID 1c5b:fa11

    #36418

    Sean
    Moderator
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic.