we have tested it. It works well.

@Lazar-Demin Thanks. we had issue with USB detection.

@Lazar-Demin always my web recovery ended up like
HTTP upload is complete.
Upgrading...

• FIRMWARE UPGRADING *
• DO NOT POWER OFF DEVICE! *

....................................................................................................................................................
....................................................................................................................................................
blocksize write incorrect block#=0!

Error: HTTP ugrade failed!

Bringing Eth0 (10/100-M) up...
HTTP server starting at 192.168.8.8 ...
HTTP server is up and running.

Boot Linux from Flash NO RESET PRESSED.

Booting image at bc050000 ...

Image Name: MIPS OpenWrt Linux-4.14.81
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1617567 Bytes = 1.5 MB
Load Address: 80000000
Entry Point: 80000000
Verifying Checksum ... Bad Data CRC

Any Idea How to solve this. I have used 5V 3A adaptor and 3.3.V LDO with 800mA current. 100uF cap to manage the current spikes.

@Zheng-Han I did one experiment.
I did
firstboot -y
sync
reboot
As I understand, the device is in factory reset. After reboot, I login.
Installed python-light python-pip

I tested Python command
root@Omega-236B:~# python
Python 2.7.18 (default, Sep 09 2024, 15:48:40)
[GCC 7.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.

reboot
I tested the python command
BusyBox v1.28.3 () built-in shell (ash)

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

Ω-ware: 0.3.4 b259

root@Omega-236B:~# python
Segmentation fault
root@Omega-236B:~#

I got segmentation fault. I did not install any extra libraries. Any Idea why it is happening.

@Zheng-Han No, SPI is not connected to anything. I use only UART, Ethernet and GPIOs as of now.
Same code works very well in most of the devices. Same design. I have used LM1117 3.3V with 100uF cap. Earlier this was not an issue. Same code is working in previous lot of Omegas.

Hi,
We are using 100s of Omega2P in field. The recent batch of omega2p got the below firmware
root@Omega-276A:~# oupgrade

Device Firmware Version: 0.3.4 b259
Checking latest version online...
url: https://api.onioniot.com/firmware/omega2p/stable
Repo Firmware Version: 0.3.4 b259
Comparing version numbers
Device firmware is up to date!

We are facing new issues. We cannot be able to run python in few boards.
root@Omega-276A:~# python
Traceback (most recent call last):
File "/usr/lib/python2.7/site.py", line 62, in <module>
ValueError: bad marshal data (unknown type code)
root@Omega-276A:~# python3
Fatal Python error: Py_Initialize: can't import _frozen_importlib
ValueError: bad marshal data (unknown type code)

Current thread 0x77f9bd0c (most recent call first):
Aborted
root@Omega-276A:~#

From Hardware point of view, all are same design and same SMPS.
I tried to to factory reset. Again same issue.

Any suggestions why few boards behave like this with python.

It would be great help. Since we are in the middle of deployment.

Thanks in advance

I have onboard Ethernet. This is custom board. all My devices are working. Few are having this issue.
I get some weird Memory issues.
I am not able to upload new firmware too.
HTTP upload is complete.
Upgrading...

• FIRMWARE UPGRADING *
• DO NOT POWER OFF DEVICE! *

....................................................................................................................................................
....................................................................................................................................................
blocksize write incorrect block#=125!

Error: HTTP ugrade failed!

Bringing Eth0 (10/100-M) up...
HTTP server starting at 192.168.8.8 ...
HTTP server is up and running.

Web failsafe mode aborted!

I suspect this issue is related to Memory.

Hi,
I am not able to successful boot of my Omega2P and I See below messages. How to Brick the Omega2P
13.303795] kmodloader: loading kernel modules from /etc/modules.d/*
[ 13.464369] RPC: Registered named UNIX socket transport module.
[ 13.470382] RPC: Registered udp transport module.
[ 13.475210] RPC: Registered tcp transport module.
[ 13.479977] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 13.499056] ntfs: driver 2.1.32 [Flags: R/O MODULE].
[ 13.585866] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 14.203248]
[ 14.203248]
[ 14.203248] === pAd = c0615000, size = 1178064 ===
[ 14.203248]
[ 14.214557] mt7628_init(FW(8a00), HW(8a01), CHIPID(7628))
[ 14.285116] Linux video capture interface: v2.00
[ 14.374445] hidraw: raw HID events driver (C) Jiri Kosina
[ 14.403932] ledchain: pwm_base=0xB0005000
[ 14.408147] ledchain: v6 - Device: /dev/ledchain2
[ 14.412916] ledchain: - PWM channel : 2
[ 14.417129] ledchain: - PWM buffer size: 12
[ 14.421365] ledchain: - Number of LEDs : 1
[ 14.425526] ledchain: - Inverted : 0
[ 14.429676] ledchain: - LED type : WS2813 GRB
[ 14.434627] ledchain: - Max retries : 3
[ 14.438777] ledchain: - Max Tpassive : 0 nS (0=chip default)
[ 14.535490] Bluetooth: Core ver 2.22
[ 14.539237] NET: Registered protocol family 31
[ 14.543799] Bluetooth: HCI device and connection manager initialized
[ 14.550253] Bluetooth: HCI socket layer initialized
[ 14.555213] Bluetooth: L2CAP socket layer initialized
[ 14.560364] Bluetooth: SCO socket layer initialized
[ 14.568171] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.573634] Bluetooth: BNEP filters: protocol multicast
[ 14.578944] Bluetooth: BNEP socket layer initialized
[ 14.591446] usbcore: registered new interface driver btusb
[ 14.601687] usbcore: registered new interface driver cdc_acm
[ 14.607514] cdc_acm: USB Abstract Control Model driver for USB modems and ISD N adapters
[ 14.620031] Bluetooth: HCI UART driver ver 2.3
[ 14.624622] Bluetooth: HCI UART protocol H4 registered
[ 14.629831] Bluetooth: HCI UART protocol BCSP registered
[ 14.639596] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 14.645691] Bluetooth: HIDP socket layer initialized
[ 14.656956] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 14.684901] nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
[ 14.783439] rt2880-pinmux pinctrl: pin io18 already requested by pinctrl; can not claim for 10005000.pwm
[ 14.792983] rt2880-pinmux pinctrl: pin-18 (10005000.pwm) status -22
[ 14.799379] rt2880-pinmux pinctrl: could not request pin 18 (io18) from group pwm0 on device rt2880-pinmux
[ 14.809267] mtk-pwm 10005000.pwm: Error applying setting, reverse things back
[ 14.823843] Bluetooth: RFCOMM TTY layer initialized
[ 14.828820] Bluetooth: RFCOMM socket layer initialized
[ 14.834109] Bluetooth: RFCOMM ver 1.11
[ 14.854392] usbcore: registered new interface driver ums-alauda
[ 14.863656] usbcore: registered new interface driver ums-cypress
[ 14.873084] usbcore: registered new interface driver ums-datafab
[ 14.882288] usbcore: registered new interface driver ums-freecom
[ 14.891675] usbcore: registered new interface driver ums-isd200
[ 14.901166] usbcore: registered new interface driver ums-jumpshot
[ 14.910494] usbcore: registered new interface driver ums-karma
[ 14.920593] usbcore: registered new interface driver ums-sddr09
[ 14.929986] usbcore: registered new interface driver ums-sddr55
[ 14.939794] usbcore: registered new interface driver ums-usbat
[ 14.952985] usbcore: registered new interface driver usbhid
[ 14.958712] usbhid: USB HID core driver
[ 14.967013] usbcore: registered new interface driver usblp
[ 14.982572] usbcore: registered new interface driver usbserial
[ 14.988691] usbcore: registered new interface driver usbserial_generic
[ 14.995464] usbserial: USB Serial support registered for generic
[ 15.015336] Driver for 1-wire Dallas network protocol.
[ 15.044970] xt_time: kernel timezone is -0000
[ 15.051895] usbcore: registered new interface driver ch341
[ 15.057674] usbserial: USB Serial support registered for ch341-uart
[ 15.067100] usbcore: registered new interface driver cp210x
[ 15.072857] usbserial: USB Serial support registered for cp210x
[ 15.082883] usbcore: registered new interface driver ftdi_sio
[ 15.088918] usbserial: USB Serial support registered for FTDI USB Serial Devi ce
[ 15.110358] usbcore: registered new interface driver pl2303
[ 15.116199] usbserial: USB Serial support registered for pl2303
[ 15.128187] PPP generic driver version 2.4.2
[ 15.136019] NET: Registered protocol family 24
[ 15.155771] usbcore: registered new interface driver snd-usb-audio
[ 15.178518] usbcore: registered new interface driver uvcvideo
[ 15.184418] USB Video Class driver (1.1.1)
[ 15.195650] usbcore: registered new interface driver option
[ 15.201404] usbserial: USB Serial support registered for GSM modem (1-port)
[ 15.214225] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 15.560945] urandom_read: 5 callbacks suppressed
[ 15.560956] random: jshn: uninitialized urandom read (4 bytes read)
20.045645] SQUASHFS error: xz decompression failed, data probably corrupt
[ 20.052634] SQUASHFS error: squashfs_read_data failed to read block 0x6c376a
[ 20.059813] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.066616] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.073457] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.080247] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.087074] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.093882] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.372097] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.378973] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.385848] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.392643] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.399469] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.406270] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.413076] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.419884] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.426705] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.433513] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.474667] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.481478] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.488384] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.495189] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.524211] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.531022] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.537923] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.544734] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.551539] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.558357] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.565171] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.571961] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.578787] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.585587] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.827877] SQUASHFS error: xz decompression failed, data probably corrupt
[ 20.834889] SQUASHFS error: squashfs_read_data failed to read block 0x6c376a
[ 20.842036] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.848849] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.855679] SQUASHFS error: Unable to read fragment cache entry [6c376a]
[ 20.862470] SQUASHFS error: Unable to read page, block 6c376a, size fed8
[ 20.869291] SQUASHFS error: Unable to read fragment cache entry [6c376a]

we have tested it. It works well.

Hi,

I tried to connect USB hub. Which is detected as Unknown Manufacturer hub

where can I add the vendor ID and Device Id

Thanks in advance

Hello,

We can able to use EC25 with omega2. Currently, LTE module access single available USB port directly. I would like to know, if we expand USB ports using USB hub, Is it possible to run LTE module on emulated usb port. I am sure USB camera works. Do I need to do any configuration changes to access right USB port. if Yes how can I access configuration related to LTE.

Thanks for any help

@crispyoz Thanks, I will try.