Omega 2+ USB Firmware Install after Brick. [Resolved]
-
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 minidocki 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 reseti'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??)
-
I connect FTDI232 to UART0 (RX0 (gpio13) to FTDI_TX, TX0 (gpio12) to FTDI_RX).
Pressfandenterto enter infailsafe mode.
Typefirstboot -y.
Wait about 20 min.
And Omega2s+ unbricks
-
@Alexandr-Didenko We can reflash (flash the same or a newer or an older or a custom - working or not working - firmware into) Omega2(+) from a USB memory device with @Colt-Burns's procedure.
firstbooton the Serial Console is "only" a Factory Reset / Factory Restore of the installed firmware.
It's same as typefirstbooton CLI (either failsafe or normal mode) or a long press of the RESET BUTTON (FW_RST).
So - I think - your Omega2S+ was not "bricked".
Did you really have to wait 20 (twenty) minutes after typing thefirstbootcommand? It looks fairly strange.
-
Just want to chime and point everyone to our documentation on the topics discussed above:
-
@Lazar-Demin It seems the common problem encountered here is in accessing the Bootloader. I'll confirm-I'm having a similar problem. While trying to access the bootloader by holding the reset during boot up with the serial connection established, it boots past option 2 to Flash firmware from USB Storage.
-
@Matthew-Lousteau Recovering from USB was always successful for me.
I use HTerm.exe for Windows. There is one quirk when selecting the option in the bootloader menu: You must not send a newline / carriage return after your choice. Just send the raw ASCII character "2".
-
@Matthew-Lousteau If @Maximilian-Gerhardt 's advice doesn't work, can you shoot a video of the behaviour? That will help us identify what's going wrong and how we can fix it.
