Omega 2+ USB Firmware Install after Brick. [Resolved]



  • @WereCatf your post on console access was a life saver today after I messed up an init.d script, thanks.



  • @Ken-Conrad said in Omega 2+ USB Firmware Install after Brick. [Resolved]:

    @cusackph I have the same problems with the Mini docks. - If the reset button or the USB -> Omega2 UART-to-serial bi-directional connection works for you with a Mini Dock, ie Putty shows any keyboard entries, then I am keen to learn how you are doing this!
    https://community.onion.io/topic/1451

    I have isolated my Mini Dock RXO problem to the Mini Dock's on-board UART not communicating with my Omega2s, the same docks work fine with an Omega1. Also sans dock, a direct serial connection via a USB to serial adapter (HAOYU) to the same Omega2s work fine.

    See also others related problems -
    https://community.onion.io/topic/1153/how-to-reset-onion-omega-2
    https://community.onion.io/topic/1321/possible-bad-omega2-and-mini-dock

    i'm also having problem with the mini dock reset button.
    i tried pressing the reset button on power dock and find that the omega2+ LED will be flashing when i press the reset button while powering it on.
    this doesn't happen when i press the reset button and power on the mini dock

    anyway to fix the mini dock ?

    i only have minidock and power dock which the minidock is the only way i can connect via serial
    and its not working at the moment



  • @Marty-Mickelson said in Omega 2+ USB Firmware Install after Brick. [Resolved]:

    The output is the same when the dock is unplugged vs plugged in and lights flashing, during the 30 sec it flashes after turning it on with the reset button pressed. I copied the list and diff'd it to make sure. Here's what I get though:

    Did you try a other USB Cable? Thin & long cable = power loss. Your hardware will not be recognized. If you check just the blank dock, it should show up if your USB Cable is ok.



  • @dennis-ctp
    this is what i get even though i'm pressing the reset button while turning it on


    / __ ___ ()_ ___ / __ __ _ ___ ___ ____ _
    / // / _ / / _ / _ \ / // / ' / -) _ / _/
    _
    /////_//// _////_/_, /_,/
    W H A T W I L L Y O U I N V E N T ? /
    __/"

    Board: Onion Omega2 APSoC DRAM: 128 MB
    relocate_code Pointer at: 87f60000
    flash manufacture id: c2, device id 20 19
    find flash: MX25L25635E
    *** Warning - bad CRC, using default environment

    ============================================
    Onion Omega2 UBoot Version: 4.3.0.3

    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:Oct 18 2016 Time:17:29:05

    icache: sets:512, ways:4, linesz:32 ,total:65536
    dcache: sets:256, ways:4, linesz:32 ,total:32768
    CPU freq = 575 MHZ
    Estimated memory size = 128 Mbytes
    Resetting MT7628 PHY.
    Initializing MT7688 GPIO system.


    • Hold Reset button for more options *

    Boot Linux from Flash NO RESET PRESSED.

    Booting image at bc050000 ...

    Image Name: MIPS LEDE Linux-4.4.42
    Image Type: MIPS Linux Kernel Image (lzma compressed)
    Data Size: 1306381 Bytes = 1.2 MB
    Load Address: 80000000
    Entry Point: 80000000
    Verifying Checksum ... Bad Data CRC



  • @dennis-ctp Haven't found the fix for the Mini Dock's issues with the Omega2s, I'm convinced this is a hardware problem - somehow the Omega2 are different enough from the original Omega that the Mini Dock doesn't work for RX0 serial connection. If you have toasted your wifi connection, but have a 3.3V TTL UART cable and a 3.3V 500mA power supply then the Omegas are easy to hard wire for a serial connection - with just the 3.3V, grounds, Rx and Tx wires.



  • actually the serial connection works for the mini dock, that's how i can get the boot info and sees that it doesn't recognize that the reset button had been pressed



  • @dennis-ctp Ahh, yes but can you do anything? With my Mini Docks I can receive data from the Omega2 but I can't SEND any keyboard commands to the Omega2, ie no command line, can't open Busybox etc, so effectively can't DO anything. The RX0 on the Mini Dock just isn't working with theOmega2 to transmit data to it. These same Omega2s have bi-directional serial communication in a Extension Dock or via the TTL UART described in my last post.



  • mine is bricked, so ofcos the command line haven't show.
    its due to the device operating system is not boot up.
    which is why i need a way to press the reset button so that i can flash it using usb.



  • @Ken-Conrad
    i think i might be facing similar problem like u mention about the minidock

    i manage to get the reset working by connecting the vin to fw_rst (gpio38)
    but it seems that the firmware doesn't wait for me to input any choices and skipped directly to reset

    i'm getting the following:

    You have 40 seconds left to select a menu option...

    Please select option:
    [ Enter ]: Boot Omega2.
    [ 0 ]: Start Web recovery mode.
    [ 1 ]: Start command line mode.
    [ 2 ]: Flash firmware from USB storage.

    Option [
    Boot Linux from Flash.

    Booting image at bc050000 ...

    Image Name: MIPS LEDE Linux-4.4.42
    Image Type: MIPS Linux Kernel Image (lzma compressed)
    Data Size: 1306381 Bytes = 1.2 MB
    Load Address: 80000000
    Entry Point: 80000000
    Verifying Checksum ... Bad Data CRC


    / __ ___ ()_ ___ / __ __ _ ___ ___ ____ _
    / // / _ / / _ / _ \ / // / ' / -) _ / _/
    _
    /////_//// _////_/_, /_,/
    W H A T W I L L Y O U I N V E N T ? /
    __/"

    Board: Onion Omega2 APSoC DRAM: 128 MB
    relocate_code Pointer at: 87f60000


    Software System Reset Occurred


    flash manufacture id: c2, device id 20 19
    find flash: MX25L25635E
    *** Warning - bad CRC, using default environment



  • Hi. Im kind of new with the Omega. I ran the firmware update, it bricked and I tried to do what you said without success. I've noticed that my problem is with the kernel.
    All tha i can see is:
    verifying checksum ok
    a lot of text like:
    [ 19.278040] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df0004: 0x5000 instead
    [ 19.287662] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df0008: 0x1000 instead
    [ 19.297284] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df000c: 0x1000 instead
    [ 19.306906] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df0014: 0x7d24 instead
    [ 19.316527] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df0018: 0xe069 instead
    [ 19.326148] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df001c: 0x3fe2 instead
    [ 19.335771] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df0020: 0xfe74 instead
    [ 19.345392] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df0024: 0xd5b2 instead
    [ 19.355014] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01df0028: 0xcc36 instead
    [ 19.364630] jffs2: Further such events for this erase block will not be printed
    [ 19.400773] jffs2: CLEANMARKER node found at 0x01dffbfc, not first node in block (0x01df0000)
    [ 19.409494] jffs2: Node at 0x01dfffe8 with length 0x00000044 would run over the end of the erase block
    [ 19.418939] jffs2: Perhaps the file system was created with the wrong erase size?
    [ 19.426700] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01e00004: 0x00a0 instead
    [ 19.436332] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01e00008: 0xc4bb instead
    [ 19.445955] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01e0000c: 0xc4bb instead
    [ 19.455577] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01e00010: 0xaccd instead
    [ 19.465199] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x01e00028: 0x8a4b instead
    [ 19.500237] jffs2: CLEANMARKER node found at 0x01e0fbfc, not first node in block (0x01e00000)
    [ 19.511496] jffs2: notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.

    Ending with
    [ 19.527264] VFS: Mounted root (jffs2 filesystem) readonly on device 31:5.
    [ 19.535241] Freeing unused kernel memory: 192K (803d0000 - 80400000)
    [ 19.541797] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
    [ 19.566820] Rebooting in 1 seconds..

    and then nothing.
    Should I open a new thread or this is ok?



  • well since this particular thread is marked resolved and if you do not think what is discussed in this thread helps fix your issue i would suggest a new thread. your issue is similar to others and i think it works out to establishing a serial connection, transferring the .bin file or maybe flashing i don't remember the details but you can ask and hope for best.



  • This guide MUST be included in the Omega2 documentation



  • You shouldn't need to do anything with a .bin file to fix a jffs2 error, unless you've flashed a .bin file for the wrong board (2 vs 2+, or worse original Omega), or you used one of the bad .bin files that were published months ago (and hopefully withdrawn??)


Log in to reply
 

Looks like your connection to Onion Community was lost, please wait while we try to reconnect.