• No labels

24 Comments

  1. Z-Yan Hou

    hi Rajkumar Narayanan, I'm following the steps. And I got stuck at step "Wait approximately 2 minutes for the Turris Omnia to flash itself with the temporary image, during which LEDs will change multiple times.". After it never boots to the temporary image. I can send you a serial log if it helps. Can you please check? 

  2. Manigandan Gopalakrishnan

    Hi Z-Yan Hou ,

    Please share serial log.

    Also, try to follow steps all over again. Please do this step "Hold down the reset button (backside, bottom centre) and plug in the power cord. Wait until the fourth LED lights up (green), then release (before the 5th LED lights up)" meticulously while USB drive connected at front USB port.

    1. Z-Yan Hou

      I have been tried multiple things and now I have Openwrt flashed. The one thing made it work is probably I updated u-boot on the device. But not 100% sure.

      Then I followed the instructions creating/formatting partition. The only difference is that mmcblk0p6 is smaller than 64MB.

      I have flashed a RDK-B build on it as well. It boots ok. One thing I found not working is setting private Wi-Fi network.

  3. Jose Ramon Diaz Martinez

    Procedure works fine just a couple of comments:

    1. I would add the step to set a different ip address in OWRT for your br-lan. Problem is that usually to acces internet you will be connected to a NAT device using 192.168.1.0/24 as well, so it is better to change it in /etc/config/network in the configuration for interface lan, you can set option ip addr '.192.168.10.1' for instance.
    2. I would set the default for U-boot before trying to flash.
    3. I would add exactly the info of the leds since this is quite critical, the leds that should switch on to flash are (POWER, 0, 1, 2), this is well documented in https://docs.turris.cz/hw/omnia/rescue_modes/ where you can find a description of the rescue modes.

  4. Gilberto Mayor

    2020-06-08 ======================================================================================================================================

    "Install a tftp server (eg. tftpd-hpa) on your computer and place the attached uboot-turris-omnia-spl.kwb file into your computer's tftp directory(eg. /srv/tftp/) and run the following commands at the u-boot prompt on Turris Omnia."


    This procedure does not work. How to adjust the ip address where the modem will download the image from the tftp server and the port?

    ## Start Code

    root@turris:/# reboot -f
    [ 468.174891] reboot: Restarting system

    U-Boot SPL 2019.07 (Oct 16 2019 - 14:15:58 +0000)
    High speed PHY - Version: 2.0
    MiniPCIe/mSATA card detection... MiniPCIe
    Detected Device ID 6820
    board SerDes lanes topology details:
    | Lane # | Speed | Type |
    --------------------------------
    | 0 | 5 | PCIe0 |
    | 1 | 5 | USB3 HOST0 |
    | 2 | 5 | PCIe1 |
    | 3 | 5 | USB3 HOST1 |
    | 4 | 5 | PCIe2 |
    | 5 | 0 | SGMII2 |
    --------------------------------
    :** Link is Gen1, check the EP capability
    PCIe, Idx 0: remains Gen1
    :** Link is Gen1, check the EP capability
    PCIe, Idx 1: remains Gen1
    PCIe, Idx 2: detected no link
    High speed PHY - Ended Successfully
    mv_ddr: mv_ddr-armada-18.09.2
    DDR3 Training Sequence - Switching XBAR Window to FastPath Window
    mv_ddr: completed successfully
    Trying to boot from SPI


    U-Boot 2019.07 (Oct 16 2019 - 14:15:58 +0000)

    SoC: MV88F6820-A0 at 1600 MHz
    DRAM: 2 GiB (800 MHz, 32-bit, 2T, ECC not enabled)
    Disabling MCU watchdog... disabled
    WDT: Started with servicing (60s timeout)
    MMC: mv_sdh: 0
    Loading Environment from SPI Flash... SF: Detected mx25l6405d with page size 256 Bytes, erase size 4 KiB, total 8 MiB
    OK
    Model: Turris Omnia
    Turris Omnia:
    RAM size: 2048 MiB
    Serial Number: 0000000E00001355
    Regdomain set to **
    Net: eth0: ethernet@70000, eth1: ethernet@30000, eth2: ethernet@34000
    Hit any key to stop autoboot: 0

    =>

    ####################################################

    (********************here type <dhcp>)

    With the network cable connected to the modem's wan port. And the tftp server on:

    # /etc/default/tftpd-hpa

    TFTP_USERNAME="tftp"
    RUN_DAEMONS="yes"
    TFTP_DIRECTORY="/srv/tftp"
    TFTP_ADDRESS=":69"
    TFTP_ADDRESS="192.168.1.253"

    TFTP_OPTIONS="--secure --create"

    ####################################################


    => dhcp
    ethernet@34000 Waiting for PHY auto negotiation to complete.... done
    BOOTP broadcast 1
    BOOTP broadcast 2
    BOOTP broadcast 3
    BOOTP broadcast 4
    .
    .
    .

    BOOTP broadcast 128
    BOOTP broadcast 129

    Retry time exceeded; starting again
    =>

    ## End Code

    How do I run the Bootloader Downgrade.
Please help me!
    2020-06-08 ======================================================================================================================================

    1. Narayanaswamy Ramaiyer

      Hi Rajkumar Narayanan

      Could you please support  Gilberto in this?

  5. Gilberto Mayor

    Hello guys, I'm waiting for help.

Thank you!

    1. Manigandan Gopalakrishnan

      Hi Gilberto,

      Please share your contact detail(slack-id/any IM id).

      1. Manigandan Gopalakrishnan

        Gilberto Mayor , I am getting IP address when i invoke dhcp command in uboot prompt

        => dhcp
neta2 Waiting for PHY auto negotiation to complete........ done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
*** Unhandled DHCP Option in OFFER/ACK: 43
DHCP client bound to address 192.168.1.37 (3779 ms)
*** Warning: no boot file name; using 'C0A80125.img'
Using neta2 device
TFTP from server 0.0.0.0; our IP address is 192.168.1.37; sending through gateway 192.168.1.1


        In your case, seems like you are not getting IP lease.

        You can try this way.

        • In PC, keep/configure your Ethernet interface in "Shared to other computers" mode. Tap the interface to bring the change into effect
        • Connect an Ethernet cable from your PC(where uboot-turris-omnia-spl.kwb file is hosted on tftp server) to WAN port of Turris Omnia
        • Then, run the following uboot commands in Turris Omnia
        dhcp
tftpboot 0x1000000 uboot-turris-omnia-spl.kwb
sf probe
sf update 0x1000000 0 $filesize


        Please update me on the results.

        Thanks.

  6. Z-Eduardo Novaes Hering

    Hi. I followed the instructions from the flashing section:




    And my serial log can be seen below:

    U-Boot SPL 2015.10-rc2 (Jan 24 2020 - 11:07:29)
    High speed PHY - Version: 2.0
    SERDES0 card detect: PEX

    Initialize Turris board topology
    Detected Device ID 6820
    board SerDes lanes topology details:
    | Lane # | Speed | Type |
    --------------------------------
    | 0 | 5 | PCIe0 |
    | 1 | 5 | USB3 HOST0 |
    | 2 | 5 | PCIe1 |
    | 3 | 5 | USB3 HOST1 |
    | 4 | 5 | PCIe2 |
    | 5 | 0 | SGMII2 |
    --------------------------------
    :** Link is Gen1, check the EP capability
    PCIe, Idx 0: remains Gen1
    :** Link is Gen1, check the EP capability
    PCIe, Idx 1: remains Gen1
    PCIe, Idx 2: detected no link
    High speed PHY - Ended Successfully
    DDR3 Training Sequence - Ver TIP-1.29.0
    Memory config in EEPROM: 0x02
    DDR3 Training Sequence - Switching XBAR Window to FastPath Window
    DDR3 Training Sequence - Ended Successfully


    U-Boot 2015.10-rc2 (Jan 24 2020 - 11:07:29 +0100), Build: jenkins-omnia-test-506

    SoC: MV88F6820-A0
    Watchdog enabled
    I2C: ready
    SPI: ready
    DRAM: 2 GiB (ECC not enabled)
    Enabling Armada 385 watchdog.
    Disabling MCU startup watchdog.
    I2C MCU watchdog failed to disable!
    Regdomain set to **
    MMC: mv_sdh: 0
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    *** Warning - bad CRC, using default environment

    PCI:
    00:01.0 - 168c:002e - Network controller
    PCI:
    01:00.0 - 11ab:6820 - Memory controller
    01:01.0 - 168c:003c - Network controller
    Model: Marvell Armada 385 GP
    Board: Turris Omnia SN: 0000000E00001355
    Regdomain set to **
    SCSI: MVEBU SATA INIT
    SATA link 0 timeout.
    SATA link 1 timeout.
    AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
    flags: 64bit ncq led only pmp fbss pio slum part sxs
    Net: neta2
    Hit any key to stop autoboot: 0
    Setting bus to 1
    BOOT RESCUE
    SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
    device 0 offset 0x100000, size 0x700000
    SF: 7340032 bytes @ 0x100000 Read: OK
    Bad Linux ARM zImage magic!
    =>


    Can you please help?

    1. Narayanaswamy Ramaiyer

      Hi Manigandan Gopalakrishnan could you please help?

  7. Z-Eduardo Novaes Hering

    Hello.


    On the section Flashing RDKB image(A Yocto Project based Distro) the following can be found:

    Create one primary partition for zImage. Create another extended partition for holding logical partitions for rootfs and /nvram.

    root@OpenWrt:/# fdisk /dev/mmcblk0
     
    Welcome to fdisk (util-linux 2.28.1).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.
     
     
    Command (m for help): p
    Disk /dev/mmcblk0: 7.3 GiB, 7818182656 bytes, 15269888 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x15488508
     
    Device         Boot Start    End Sectors   Size Id Type
    /dev/mmcblk0p1 *     2048  35327   33280  16.3M  c W95 FAT32 (LBA)
    /dev/mmcblk0p2      36864 561663  524800 256.3M 83 Linux



    But in the Turris I have here, fdisk shows the following:


    root@turris:/# fdisk /dev/mmcblk0

    Welcome to fdisk (util-linux 2.34).
    Changes will remain in memory only, until you decide to write them.
    Be careful before using the write command.


    Command (m for help): p
    Disk /dev/mmcblk0: 7.29 GiB, 7818182656 bytes, 15269888 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x00000000

    Device Boot Start End Sectors Size Id Type
    /dev/mmcblk0p1 16 15269887 15269872 7.3G 83 Linux

    Command (m for help):


    How can I shrink /dev/mmcblk0p1 so there is space left for the new Yocto RDK built images, as requested in the section mentioned above?

    Can you please help?


    1. Narayanaswamy Ramaiyer

      Hi Manigandan Gopalakrishnan could you please help?

    2. Manigandan Gopalakrishnan

      Hello Eduardo,

      Looks like Openwrt Medkit image is not flashed correctly. Following prompt suggests that your Turris Omnia still has stock image

      root@turris:/#


      Can you please try once again to follow steps given under Flashing section above. This will clear Flash storage and creates two partitions leaving lot of free space.

      Note that you should get openwrt linux prompt as follows after successful openwrt(Fail safe kernel) flashing.

      root@OpenWrt:/#

      Kindly, let me know on progress.


      Thanks.

      1. Z-Eduardo Novaes Hering

        Hello, Manigandam! Thank you for your answer.

        Indeed the problem relies on the flashing. I have submitted a post about it two posts above this one. It is related to:

        Bad Linux ARM zImage magic!
        =>

        1. Manigandan Gopalakrishnan

          Hi Z-Eduardo Novaes Hering ,

          To fix this error "Bad Linux ARM zImage magic!" , can you please try with another version of sysupgrade and medkit image

          https://downloads.openwrt.org/releases/18.06.5/targets/mvebu/cortexa9/openwrt-18.06.5-mvebu-cortexa9-turris-omnia-sysupgrade.img.gz

          https://downloads.openwrt.org/releases/18.06.5/targets/mvebu/cortexa9/omnia-medkit-openwrt-18.06.5-mvebu-cortexa9-turris-omnia-initramfs.tar.gz

          Kindly update me on results.

          FYI, meanwhile i am exploring on how to shrink currently active partition(/dev/mmcblk0p1 - btrfs filesystem i guess)

          Thanks.

          1. Z-Eduardo Novaes Hering

            Hello, Manigandan Gopalakrishnan

            Thank you for your message.

            I downloaded both files, added them to the ext2 pendrive and tested the procedure, but got the same result:

            U-Boot SPL 2015.10-rc2 (Jan 24 2020 - 11:07:29)
            High speed PHY - Version: 2.0
            SERDES0 card detect: NONE

            Initialize Turris board topology
            Detected Device ID 6820
            board SerDes lanes topology details:
            | Lane # | Speed | Type |
            --------------------------------
            | 0 | 5 | PCIe0 |
            | 1 | 5 | USB3 HOST0 |
            | 2 | 5 | PCIe1 |
            | 3 | 5 | USB3 HOST1 |
            | 4 | 5 | PCIe2 |
            | 5 | 0 | SGMII2 |
            --------------------------------
            :** Link is Gen1, check the EP capability
            PCIe, Idx 0: remains Gen1
            :** Link is Gen1, check the EP capability
            PCIe, Idx 1: remains Gen1
            PCIe, Idx 2: detected no link
            High speed PHY - Ended Successfully
            DDR3 Training Sequence - Ver TIP-1.29.0
            Memory config in EEPROM: 0x02
            DDR3 Training Sequence - Switching XBAR Window to FastPath Window
            DDR3 Training Sequence - Ended Successfully


            U-Boot 2015.10-rc2 (Jan 24 2020 - 11:07:29 +0100), Build: jenkins-omnia-test-506

            SoC: MV88F6820-A0
            Watchdog enabled
            I2C: ready
            SPI: ready
            DRAM: 2 GiB (ECC not enabled)
            Enabling Armada 385 watchdog.
            Disabling MCU startup watchdog.
            Regdomain set to **
            MMC: mv_sdh: 0
            SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
            *** Warning - bad CRC, using default environment

            PCI:
            00:01.0 - 168c:002e - Network controller
            PCI:
            01:00.0 - 11ab:6820 - Memory controller
            01:01.0 - 168c:003c - Network controller
            Model: Marvell Armada 385 GP
            Board: Turris Omnia SN: 0000000E00001355
            Regdomain set to **
            SCSI: MVEBU SATA INIT
            SATA link 0 timeout.
            SATA link 1 timeout.
            AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
            flags: 64bit ncq led only pmp fbss pio slum part sxs
            Net: neta2
            Hit any key to stop autoboot: 0
            Setting bus to 1
            BOOT RESCUE
            SF: Detected MX25L6405D with page size 256 Bytes, erase size 64 KiB, total 8 MiB
            device 0 offset 0x100000, size 0x700000
            SF: 7340032 bytes @ 0x100000 Read: OK
            Bad Linux ARM zImage magic!
            =>


            I tried that with two different pendrives, from two different manufacturers.

            Do you have an idea on what could be wrong?

            Thanks again for your kind attention.


            1. Manigandan Gopalakrishnan

              Z-Eduardo Novaes Hering ,

              FYI, I am trying to get serial console log from working scenario.

              Also meanwhile, sought help from other experts to fix your issue.

              It would be convenient if you come on RDKM slack. Kindly consider.


              Thanks.

              1. Manigandan Gopalakrishnan

                Hello Z-Eduardo Novaes Hering,

                Another developer Z-Liam Clark faced same "Bad Linux ARM zImage magic!" issue while flashing Openwrt-18.06.2. But liam managed to flash latest version Openwrt-19.07.3


                Medkit URL: http://downloads.openwrt.org/releases/19.07.3/targets/mvebu/cortexa9/omnia-medkit-openwrt-19.07.3-mvebu-cortexa9-cznic_turris-omnia-initramfs.tar.gz

                Upgrade URL: http://downloads.openwrt.org/releases/19.07.3/targets/mvebu/cortexa9/openwrt-19.07.3-mvebu-cortexa9-cznic_turris-omnia-sysupgrade.img.gz


                Please try to flash Openwrt-19.07.3 and update me so that i will update this wiki page.

                1. Z-Howard Teece

                  I'm trying this and I get exactly the same result.

                  I previously had an old RDK image that didn't have the Flash util, so decided to re-flash a new image from scratch. And now I have a box that doesn't function.


                  1. Manigandan Gopalakrishnan

                    Hello Z-Howard Teece ,

                    In openwrt forum, i raised question on Openwrt-19.07.3 release build as Openwrt-19.07.3 is latest one and it should not throw "Bad Linux ARM zImage magic!".

                    I will let you know when i get support from openwrt.


                    FYI, we have plan to generate RDK based medkit image for Turris Omnia target and that will solve these issues.

                    1. Manigandan Gopalakrishnan

                      Hello Z-Howard Teece ,

                      Please share your board revision (https://docs.turris.cz/hw/omnia/revisions/).

                      1. Rajkumar Narayanan

                        Hello Z-Howard Teece ,

                        Just a thought.

                        Can you please try with this version(18.06.8) in your turris omnia device(older revision i guess)

                        Upgrade URL: https://downloads.openwrt.org/releases/18.06.8/targets/mvebu/cortexa9/openwrt-18.06.8-mvebu-cortexa9-turris-omnia-sysupgrade.img.gz

                        Medkit URL: https://downloads.openwrt.org/releases/18.06.8/targets/mvebu/cortexa9/omnia-medkit-openwrt-18.06.8-mvebu-cortexa9-turris-omnia-initramfs.tar.gz

  8. Manigandan Gopalakrishnan

    FYI,

    I suppose, this is the working combination with respect to u-boot and rescue image in Turris Omnia.

    Older u-boot(version 2015.10-rc2) <--> non-FIT rescue image (For example: legacy rescue image)

    Newer u-boot(version 2019.07) <--> FIT rescue image (For example: FIT rescue image)

DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.