Unable to bootm current OpenWRT image

overzelus
 
Posts: 5
Joined: Sat Sep 29, 2018 4:20 am

Unable to bootm current OpenWRT image

Sat Sep 29, 2018 4:39 am

Instead of risking a failed upgrade, I've been attempting to use u-boot to load an image over kermit and use the bootm to test.

Per this post, it's not going well.
I've been using a fresh git clone of the OpenWRT repository and a Kubuntu 18.04 host system.
I think I've managed to satisfy OpenWRT's library requirements, and the image appears to build successfully.

I copy:
/home/zelus/openwrt/bin/targets/ramips/mt76x8/openwrt-ramips-mt76x8-vocore2-squashfs-sysupgrade.bin
to the Vocore2 (no dock) and attempt to bootm.

This is what happens:
Code: Select all
============================================
Ralink UBoot Version: 4.3.0.0
--------------------------------------------
ASIC 7628_MP (Port5<->None)
DRAM component: 1024 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 128 MBytes
Flash component: SPI Flash
Date:Jun 25 2016  Time:22:54:33
============================================
icache: sets:512, ways:4, linesz:32 ,total:65536
dcache: sets:256, ways:4, linesz:32 ,total:32768
RESET MT7628 PHY!!!!!!
Please choose the operation:
   0: Load system code then write to Flash via SERIAL.
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   5: Load system code then write to Flash via USB Storage.
   7: Load Boot Loader code then write to Flash via Serial.
   8: Start Web Server to load system code.
   9: Load Boot Loader code then write to Flash via TFTP.
gpio trigger enabled
GPIO 46 used to trigger webpage
Hold button for between 3 seconds and 6 seconds
        then release to trigger webpage to load image
Hold button for between 6 seconds and 9 seconds
        then release to trigger loading image from USBSTORAGE
GPIO 46 is low
 8
You chose 4

 0

4: System Enter Boot Command Line Interface.

U-Boot 1.1.3 (Jun 25 2016 - 22:54:33)
VoCore2 > loadb
## Ready for binary (kermit) download to 0x80100000 at 115200 bps...

(Back at Gemini)
----------------------------------------------------
(/home/zelus/) C-Kermit>send ~/boot.bin
(/home/zelus/) C-Kermit>connect
Connecting to /dev/ttyUSB0, speed 115200
 Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
## Total Size      = 0x003802c1 = 3670721 Bytes
## Start Addr      = 0x80100000
VoCore2 > bootm
## Booting image at 80100000 ...
   Image Name:   MIPS OpenWrt Linux-4.14.71
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    1542756 Bytes =  1.5 MB
   Load Address: 80000000
   Entry Point:  80000000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... LZMA ERROR 1 - must RESET board to recover
******************************
Software System Reset Occurred
******************************
*** Warning - bad CRC, using default environment


Am I doing anything obviously wrong? Do I really need to use a 14.04 VM to work with this code?

overzelus
 
Posts: 5
Joined: Sat Sep 29, 2018 4:20 am

Re: Unable to bootm current OpenWRT image

Mon Oct 01, 2018 12:13 am

After a few experiments, I realize this image apparently isn't in a format that's capable of being bootm'd.

Still trying to understand OpenWRT's fairly unique filesystem layout along with the boot architecture and build environment.

Knowing that I can use u-boot option 0 and the 20170527V.bin image to recover after a weird update has been enough to allow me to continue forward.

Vonger
 
Posts: 679
Joined: Sun Oct 19, 2014 6:00 am

Re: Unable to bootm current OpenWRT image

Wed Oct 03, 2018 9:10 am

mediatek uboot you need to setting up some env about file size...
please check its source code at github.com/vonger/

Return to VoCore2/Lite/Ultimate

Who is online

Users browsing this forum: No registered users and 2 guests