Posts made by jossvall

Update on this case:

After verifying with the oscilloscope, I found a voltage drop of 250µs, which explains why the Omega shuts down, since the drop reaches 2V and the Onion regulator cannot raise the voltage.

This makes it clear that it is not a PIN error but a problem in the regulation stage.

Now another question arises: why does it restart with version 18, but with version 23 the board remains off? Is there a parameter that allows the Omega to restart in case of a voltage drop or to shut down?

Thanks to colleague @luz for your help

@luz Hi, thank you so much for your help.

I'll run tests with an oscilloscope to analyze the voltage drops.

The scenario in detail is this:

Normally, the modem starts automatically. I have a script in "/etc/init.d/modem" that runs when the system is loading and starting programs. If it does this at this point, there's no problem; the modem is powered on and then starts.

But if the startup occurs after the operating system has loaded everything, that is, after:

Fri Mar 22 22:11:21 2024 daemon.info procd: - init complete -

simply setting the regulator's power pin high shuts down the modem. I recently discovered that this only happens if the modem is connected; if the modem is disconnected, this sudden shutdown doesn't occur. Furthermore, the modem has a separate regulator, which makes it even stranger to me. I don't understand why it works with version 18 but not with version 23, even though it has the same PCB.

Update on this issue.

I see that the problem isn't with pin 43. I've already tested pins 36 and 14, and the same thing happens. When I try to enable the modem's voltage regulator, the Omega turns off. Ironically, this doesn't happen with version 18. What did they break on the way to version 23?

Hello community

I hope you are all doing well.

I'm reaching out to you regarding the following issue:

I currently have approximately 500 devices running OpenWRT version 18. We are working on updating to version 23.05, and I've already completed this process, generating the image with the custom programs.

During testing, I've encountered very strange behavior. Pin 43 (GPIO) is used to activate the PMIC of a modem.

When the modem boots with the system, everything works (while the system LED is blinking). However, if the modem needs to be restarted after the system boots, the Omega 2SP suddenly shuts down. There is no serial output indicating a power-off; everything simply shuts down, as if the power were disconnected internally.

This doesn't happen with version 18, only with version 23. Can anyone help me with this?

NOTE:

Perform the test using echo 1 > /sys/class/gpio/gpio43/value

If I type 0 there is no problem, but if I type 1 the card shuts down abruptly. However, this only happens when the system has booted and the system LED is on.

After performing several tests, I found that the problem in the short communication distance was due to the wifi antenna.

I tried with the antenna that comes with the evaluation board of the Omega2s+ and I stopped losing information.

Does anyone know what the part number of this antenna is?

Hello, good day to everyone,

I have been working for a while on a project using an omega 2s+, to which several ESP12Fs (ESP8266) are connected, this has worked very well when I have the ESP12Fs in the same room, but when I start to move them away (8 to 12 meters ) I start to lose communication.

Initially I used an antenna design on the same PCB, today I used an external antenna but the results did not improve (I had connected the omega 2s+ through a 0 ohm resistor in case I ever needed to use an external antenna)

Given this, I must return to the design table, for them I would like you to help me with some questions:

• Is the maximum power of the onion enabled by default? Or is it limited by a parameter in the system configuration?
• Is it possible to amplify the wifi signal of the omega 2s+? Can you provide me with a component part number to make this change?

@EERoarEE you could unboot network at system boot:

rm /etc/rc.d/S20network

Note: keep in mind that this will remove the symbolic link from the network boot, and it will not restart the network unless you re-create that symbolic link. use that command at your own risk.

I think you could also add a script at the end of the boot, so that it deactivates it at the end of loading all the programs.

You could also add a task to the cron that is responsible for downloading that process.

@EERoarEE You could disable the network process and test if you still have RF signals

/etc/init.d/network stop

Hi good day,

The omega2s + has a PCIe port, I am thinking of using this port to connect a 4G modem (Quectel EM120R or EM160R) but I have not seen information about this, does anyone know if the operating system has support for this port?

I am working with a custom PCB for an omega2s +.
in the device there is an omega2s + a GPS and a modem and a 4 channel optocoupler to handle GPIO signals.

they have been in testing for about 2 months today in a normal check routine run logread "and I was surprised, the log was full with the following message

Thu Jul 15 16:28:32 2021 kern.warn kernel: [102649.066406] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:32 2021 kern.err kernel: [102649.072469] mmc0: error -22 whilst initialising SDIO card
Thu Jul 15 16:28:32 2021 kern.warn kernel: [102649.079851] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:32 2021 kern.err kernel: [102649.085953] mmc0: error -22 whilst initialising MMC card
Thu Jul 15 16:28:32 2021 kern.warn kernel: [102649.166957] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:32 2021 kern.err kernel: [102649.173044] mmc0: error -22 whilst initialising SDIO card
Thu Jul 15 16:28:32 2021 kern.warn kernel: [102649.181002] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:32 2021 kern.err kernel: [102649.187098] mmc0: error -22 whilst initialising MMC card
Thu Jul 15 16:28:33 2021 kern.warn kernel: [102649.267201] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:33 2021 kern.err kernel: [102649.273270] mmc0: error -22 whilst initialising SDIO card
Thu Jul 15 16:28:33 2021 kern.warn kernel: [102649.281234] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:33 2021 kern.err kernel: [102649.287316] mmc0: error -22 whilst initialising MMC card
Thu Jul 15 16:28:33 2021 kern.warn kernel: [102650.106696] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:33 2021 kern.err kernel: [102650.112772] mmc0: error -22 whilst initialising SDIO card
Thu Jul 15 16:28:33 2021 kern.warn kernel: [102650.120103] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:33 2021 kern.err kernel: [102650.126184] mmc0: error -22 whilst initialising MMC card
Thu Jul 15 16:28:34 2021 kern.warn kernel: [102650.206946] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:34 2021 kern.err kernel: [102650.213015] mmc0: error -22 whilst initialising SDIO card
Thu Jul 15 16:28:34 2021 kern.warn kernel: [102650.221053] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:34 2021 kern.err kernel: [102650.227140] mmc0: error -22 whilst initialising MMC card
Thu Jul 15 16:28:34 2021 kern.warn kernel: [102650.307188] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:34 2021 kern.err kernel: [102650.313262] mmc0: error -22 whilst initialising SDIO card
Thu Jul 15 16:28:34 2021 kern.warn kernel: [102650.321487] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:34 2021 kern.err kernel: [102650.327584] mmc0: error -22 whilst initialising MMC card
Thu Jul 15 16:28:34 2021 kern.warn kernel: [102651.146325] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:34 2021 kern.err kernel: [102651.152392] mmc0: error -22 whilst initialising SDIO card
Thu Jul 15 16:28:34 2021 kern.warn kernel: [102651.159595] mtk-sd 10130000.sdhci: no support for card's volts
Thu Jul 15 16:28:34 2021 kern.err kernel: [102651.165680] mmc0: error -22 whilst initialising MMC card

the log size is 1020 KB and you just see that message over and over again. After a quick search in google, I saw several forums where they relate this error to the support for SD, but in my PCB it is not and using any of these pins, these pins are floating.

• Does anyone have any idea of ​​the reason for that error?
• should I use pullup / pulldown resistors on the SD lines?

NOTES:
Regardless of the error that the kernel is reporting, the omega2s + is working, all the programs that I compile to perform the tasks that are needed are also working well, I just want to make sure of the cause of the problem, since the device is in its final stage of tests and is about to go into production.

also restart the omega2s + but the kernel keeps generating the error message.

@Franmcm said in Help for project:

omega 2+

Hi Franmcm, the omega2 + is an excellent choice for your hardware and software requirements. If you have used raspberry you will not have problems with omega2 +.

@francisco-vieira I'm sorry I read it wrong, you're right, the omega 2 only has two ports, what did you do to disable the omega console?

port ttyS0 is used by the Omega2s serial console.

Have you considered using the ttyS1 or ttyS2 port for communication with the modem?

@SimonPR If the datasheet specifies a configuration, it is best to follow it

In both configurations they add the 50 ohm resistance, I would think that it is limiting the current that reaches the VDD flash pin, but it may have other critical reasons related to the correct functioning of the Omega

@Nagarjuna-Reddy It is very difficult to help you if you do not provide technical information about your circuit.

Are you using a USB to TTL converter? What happened to ttyUSB0 and ttyUSB1?

Have you looked at the system log to see if something is wrong?

@Nagarjuna-Reddy I see that you published in another post, and I think you were able to make your custom board start correctly, you should post the solution here, so that other people can get feedback from the experience.

@Nagarjuna-Reddy What omega are you using? Are you using an expansion dock? Are you connecting the GPS through a HUB?

@dbell Well let's go in parts,
You mentioned that your PC has a serial port which has a DB9 connector, Be careful that this connector is RS232 which is very different from TTL, you can cause damage to the omega if you connect it directly.

Most likely that COM1 refers to the native serial of your PC.

In the device manager of your PC do you see more COM ports apart from COM1?
do you have unknown devices?

@dbell Are you connecting the PC to the micro USB of the Omega2?