@jossvall to disable the omega console just follow this link https://www.hackster.io/sidwarkd/free-up-the-serial-port-on-the-onion-omega-7b3849

Hi @crispyoz

This was the result for lsof.

root@Omega-4F7D:~# lsof | grep ttyS0
root@Omega-4F7D:~#

It seems no process is using the ttyS0 and I have the

root@Omega-4F7D:~# gcom -d /dev/ttyS0 info

Wireless WAN Modem Configuration

Product text:

comgt 14:14:00 -> -- Error Report --
comgt 14:14:00 -> ----> ^
comgt 14:14:00 -> Error @187, line 10, Could not write to COM device. (1)

@jossvall Hi, on Omega 2+ model we just have 2 tty port available and we are using the 2. One for 3g (ttyS0) and another to communicate with another CPU (ttyS1).

Hi @crispyoz thank you again for your quick answer. I already try the netstat -utnp but the result it's the connections TCP/UDP Onion have and not the pid of the process that is using the tty. Lsof is not natively on Onion Omega 2+ version I have. Do you see anything that can close this "zombie" connection?

This is the error: comgt 10:41:55 -> Error @118, line 9, Could not write to COM device. (1)

@crispyoz thank you for your quick answer. When I do the ps command I don't see any process that is using the tty port. Do you have any idea what system process can be using the tty port? That tty port is controlled automatically by the system (pppd and chat) and what I'm doing is just enable or disable the modem by updating the /etc/config/network file.

Hi.

Product in use: Onion Omega 2+ (with custom hardware)
Firmware in use: 0.2.2 b202
Description:

I'm using a 3G modem which is connected to ttyS0 port and it's controlled directly by the pppd/chat. What happens is sometimes the ttyS0 port gets "blocked" or "freeze" and the system can't do anything with it unless I made a reboot on the Onion (only way I find to put it working again). Has this happened to anyone else?

I'm trying to find some information on how to reset or restart or unbind the port but until now I didn't find nothing. Do you have any solution for that?

Thank you in advance.

@crispyoz thank you so much for your suggestion. I think we will follow your suggestion and add some logic on our service to guarantee all the required resources/services are up before we start our service.

Thank you so much my friend.

@crispyoz ok, I will try to use the SD Card and not the internal flash for internal tests. The difficult for us has been that happens randomly and It's difficult to reproduce in laboratory (we have more than 30 Gateways on tests). Relatively to the power issue, we are already studying if the problem is there.

Thank you so much for your help my friend.

@luz It's true, it was being a tough problem since 3 months ago.

Relatively to your first suggestion, the GPRS or the Ethernet write the same amount of data with the same frequency. I will try to calculate that and get you back as soon as possible.

Relatively to your second and third suggestion, we already are investigating this possible hardware issues and trying to get a solution to that. As you can imagine, with more that 500 installations done right now, we pretend first to understand if a software solution is possible. If not, and if we find a hardware solution (against the interferences or changing the equipment power supplies) we will advance to change all the > 500 Gateways.

After we can prove there is related to the interferences I think your software work around suggestion can be a good solution for that.

Do you see another things we can do for protect the Onion from the interferences (by software)?

Thank you my friend.

@crispyoz no, I didn't tried with SD Card because I have more than 500 installations done and I'm trying to find a solution or something that mitigate the problem via software (remotely I have access to all Gateways).

Thank you for all your help on this clarification @crispyoz. But maybe the most fail safe way to guarantee all the needed services are up is to put my service on the last position of START?

Hi,

Product in use: Onion Omega 2+ (with custom hardware)
Firmware in use: 0.2.2 b202
Description:

To give some context to the situation itself, I will briefly explain the product we created. We created a Gateway based on Onion Omega 2+ where we use the following resources provided by it:

Serial 0 (GPIO 13/12) - It is being used for an external GSM module (115200 bps)
Serial 1 (GPIO 45/46) - It is being used to talk to an external CPU (500000 bps)
Ethernet
GPIO 03/11/15/16 - Are being used as output
GPIO 02/17 - Are being used as input
FW RST (GPIO 38) - It is being used to reset the Onion Omega 2 +
GND/3.3V - Power

The warning mentioned in the subject only happens when we are using Modem-3G to output data to a platform (developed by us). Another additional information is that our solution saves every 5 minutes (minute 0, 5, 10, etc.) some data on flash. Through the "logread" I was able to discover that sometimes the error " kern.warn kernel: [ 854.947376] jffs2: Newly-erased block contained word 0x0 at offset 0x01180000" occurs on that saves on flash and after this warning if we restart the Gateway it will no longer start (Onion is damaged).

Can you help troubleshooting the problem? Someone already managed this problem? Also, how does it just happen with GPRS?

This situation is happening sometimes in all the Gateway with GPRS we have (>500).

Thank you in advance.

Hi,

Product in use: Onion Omega 2+ (with custom hardware)
Firmware in use: 0.2.2 b202
Description: We have created a service to start/stop/restart our solution on init.d with the sequence configuration START=90 and STOP=10. What the sequence configuration you suggest for the START and STOP? Our solution is a completed solution that uses almost all the services existents (3G, NTPD, GPIO, etc.).

Thank you in advance.

@crispyoz thank you

@crispyoz thank you again. What firmware version do you suggest? The most recent or the most stable?

@crispyoz thank you for all you patient to answer me. But, every week, 1 or 2 Onion Omega 2+ are freezing and I'm afraid on what is happening. Based on your experience, do you think an update for the new firmware can solve this issue? Or help to solve it?

@crispyoz thank you again. I just proceed to https://docs.onion.io/omega2-docs/Firmware-Flashing-Web-Recovery.html and it worked on the 3 I have with me. The problem, is the other 500 already installed that I want to avoid that problem.

@tjoseph1 thanks for the reply. The point here is that I have 500 installations (which started in 2018) that would need updating (which is not the problem) but would have to ensure that it would solve the problem. Do you think it will solve?

@crispyoz thanks for the reply. As I mentioned above, the factory reset solution works to solve the problem. What I am looking for, are possible causes for these problems (for example, outdated version) as I have more than 500 installations made with the product.