@Jim-W The configuration changes you show are correct, personally I prefer to place them in the wireless config but either is fine. Adding the route to rc.local is not required.

@Jim-W The resolv.conf being overwitten will be caused by dnsmasq but if you can't ping then that is the issue that need to be sorted.

Can you ping 192.168.1.1 ?

Please post /etc/config/wireless and the output of route -e

@Jim-W It looks ok to me, so I wonder if the issue is your DNS. Can you ping 8.8.8.8 and 8.8.4.4 ?

If receive a response then this is s DNS setup issue. When you use a static IP your're not using DHCP protocol which not only provides your IP but also provides your DNS configuration. Edit /etc/resolv.conf and add your DNS configuration here. If you're not sure which DNS to use you can use Google's which are the IPs I asked you to ping above. Like so:

Interface wwan

nameserver 8.8.8.8
nameserver 8.8.4.4
search localdomain

@crispyoz said in Onion2s+ Reflashes itself randomly.:

Take a look at /etc/init.d/avahi-daemon for a simple example of how to setup a startup script. Alternatively you can add the command(s) to your /etc/rc.local

@wflynn Nothing stands out to me as problematic, this looks like a standard system other than you have a USB device installed, which should not be an issue. So we need to look at why/how/if the system is being corrupted.

You mentioned running your script(s) in cron at boot, I assume you are using @reboot prefix in your crontab, correct?
Have you tested using rc.local or procd? Take a look at /etc/init.d/avahi-daemon for a simple example of how to setup a startup script. Alternatively you can add the command(s) to your /etc/rc.local but be sure you add the ampersand after the command(s) so as to background the script, otherwise you may lose your command prompt, eg:

/usr/sbin/myprogram -c some parameter &

I'd also be interested to see the code to how you are writing to file in case there is something potentially corrupting your file system.

These are my best guesses in the absence of more specific details of the script.

@nsmith You need an antenna of some sort, the Omega2+ has an antenna on it's little PCB, but the Omega2S is not on a PCB so it has no antenna. You have a choice a UFI antenna or an SMD antenna, the UFI antenna may give you better wifi but it's plugged in to the Omega2S UFI connector then you have to mount it somewhere. Just google UFI antenna there are loads available, I've tried several and they all functioned fine but personally I use an SMD antenna so it can be mounted discreetly on the board, the DigiKey part # is 712-1010-1-ND, they have 450,000+ in stock.

Your link was to the Omega2S which has 64MB RAM and 16MB Flash, if you need more you can use Omega2S+ which has 128MB RAM and 32MB Flash same as the Omega2+ you have been referring to in your recent posts.

https://www.digikey.com/en/products/detail/onion-corporation/om-o2sp/9922958

Here is the Omega2 reference schematic which helps you to design your PCB to use the Omega2S.

https://github.com/OnionIoT/Omega2/blob/master/Schematics/Omega2S-Reference-Schematic.pdf

@wflynn The Omega2 will write a file to the location on the file system you specify, so the first step is to determine where that is and provide that information here.

Are you booting the Omega2 from USB?

The Omega2 doesn't reflash itself, but perhaps you have a cron job set up to make it do so, which would be a risky strategy. Post the output of each of these commands:

oupgrade -v
mount
crontab -l
cat /etc/rc.local
ls -la /etc/init.d

@nsmith Exactly the same firmware image, you just have more GPIO, UART and PWM exposed.

@wflynn Not sure why you would be running a script from cron at boot time. Typically you would use procd or rc.local. Perhaps you can provide more detail on what your script does and how you have the device configured to run the script.

issue 2 sounds like there may be an issue in your script, I've never seen the firmware reflash itself, that would be quite a sight. My suspicion is that your file system may be getting mucked up, but we need more detail on what your script does in order to be able to troubleshoot further.

@nsmith as much as I love your optimism, I'm not sure that a "silicon bug" can be resolved by optimism and a DTS. Omega2 uses MT7688 not MT6821, the SPI issue is well documented and minds greater than mine have yet to find a software solution other than that detailed by @luz