@lorenzooo I assume when you say python pip modules they're installed with pip and not as python3-* packages using opkg? If that's the case, I agree with @crispyoz, the cloning firmware method is the best way to go here.

@Oziesin it looks like your device is running the Omega2 LTE firmware. In this firmware, the device is omega2lte. However, it's compatible with all omega2p firmware. Add a -f argument to your sysupgrade command and it should work fine.

replying to an old thread i know... @sks @crispyoz it seems that the behaviour you describe puts the omega's in our application over the edge sometimes. keeping the "sta" part switched on without a wifi network to "connect to" in our case apparently eats so much resources (or something else happens) that it renders our application crippled. we are currently troubleshooting franticly because we start getting devices back from customers, sometimes even the omega's AP SSID disappears from the air and the omega needs a reboot to "fix" it. the serial console keeps working in this case, so luckily there is a way to investigate further. i really hope someone finds a way to make this more reliable. For now we will be shipping our devices in 'ap' mode instead of 'apsta' if you're interested, i just opened a help request about this at https://community.onion.io/topic/4659/wifi-driver-seems-to-crash-when-wifi-network-unavailable. cheers tony always open to suggestions

@crispyoz cheers for the inspiration and cheers to you!

@Nagarjuna-Reddy I'll see if I can duplicate your problem, but I do not understand your reply to @Lazar-Demin. Also what is the battery rating? 3.7v XXmA ?? XX is? As @Lazar-Demin asked, please follow these steps and report the results. Switch off Omega-LTE Disconnect USB power Switch on Omega-LTE Does the Omega-LTE boot and function correctly or does it restart when it is booting up? Assuming this boots and functions OK then we do a second test. Boot Omega-LTE while connected to battery only, wait until Omega has completed boot and is fully functional Connect USB power. Does the Omega-LTE restart?

@Nagarjuna-Reddy https://openwrt.org/docs/guide-user/services/snmp/mini_snmpd

@Nagarjuna-Reddy OpenWrt init.d is well documented, what have you tried that is not working?

@Ghofran-Daoues this is not really a question for this forum, it's really for a libmodbus forum. However, your error indicates it cannot connect to port 502 of the device. There can be a few reasons for this, the first things I would look at are 1) perhaps the device is not accessible on your network; 2) the device is not listening on port 502. To check 1, see if you can ping the device (ping <ip address>) To check 2, (assuming check 1 passes) check your modbus device is listening on port 502 using nmap (nmap -p 502 <ip address>) nmap should report the port is "open" but if it shows as closed, there's your problem, if it reports as "filtered" there is probably a firewall blocking you.

@ab09 We need to know what firmware version you are using. Make sure you have you updated to the latest firmware version. Perform a factory reset to you can be sure it is nothing you have done to mess up the configuration. When booting do you see the Warp Core splash screen? Some people have had issues connecting to WiFi if they have the device set to US frequencies. In /etc/config/wireless look for this : config wifi-device 'radio0' option type 'ralink' option variant 'mt7628' option country 'US' Remove it and reboot. If that doesn't fix the issue, try fixing the channel instead of option channel 'auto' set it to a valid channel for your region. Channel 11 is usually good but your situation may differ so you can try anything in the range 1 - 11 for 2.4Ghz

@Nagarjuna-Reddy Can you please outline what you're trying to accomplish? If you're trying to run the OS from the eMMC storage: You've succeeded! By using the Omega2 Pro firmware, it has set everything up to run the OS from eMMC. This is the case with your device. The OS is running from the eMMC, you can tell by this line in your df -h command output: This is mounted as the root / and there's 7.1 GB total size with 6.3 GB available. You can confirm this by running df -h /. This will report the available space on the root filesystem. If you're trying to run the OS from the internal flash, and use eMMC as external storage: You'll need to flash the Omega2+ firmware to your device. To flash the Omega2+ firmware, follow the instructions in this documentation article: http://docs.onion.io/omega2-docs/manual-firmware-installation.html A new notes: In step 1, download the omega2p firmware with the highest build number. As of April 29, 2020, that's omega2p-v0.3.2-b239.bin In step 2, you'll need the -F option since you are attempting to flash a device with Omega2 Pro firmware with Omega2+ firmware If that's not what you're trying to accomplish Then please let me know: What you're trying to accomplish What is your expected result What you've tried And how it turned out Regarding your comment on RAM: @Nagarjuna-Reddy said in Onion omega 2S pro flash memory issue.: but it is showing me 6.6MB only and temps even RAM size also showing less.. The output from the free command shows 124920 kB, that's ~ 128MB If you're curious about how tmpfs works, read more here: https://www.denx.de/wiki/view/DULG/FilesystemTMPFS