@Lazar-Demin It was in the 22 Beta I was playing with on that day. As I recall I had downloaded the firmware on the day before, so whatever revision was current on 17th May. I've moved on to 23.05 now so no longer have the 22 stuff to check. Next time I'll remember to include the version details. Sorry for the newbie omission.
Hi all,
As a follow up to this, the Omega2 LTE has been working well utilizing power through the GPIO pins.
We have discovered an issue however with using a LiPo battery as a back up.
The LiPo happily runs the board as expected, but the charging circuit is not working.
Is there a way we can power the charging circuit from the 5V GPIO pins?
@crispyoz Thanks! That's an idea - I could probably just do a bunch of register level acces to initialise the display over i2c and put up something. I'll need to do a bit of learning on uboot
For future reference. I had the same issue on an Omega2Pro yesterday. The factory partition was was messed up, I cloned another device and this fixed the issue, but perhaps the radio is not perfectly calibrated.
@MK said in Onion Memory structure:
Does anybody know where I could find the Omega specific flash layout (just out of curiosity in order to cross check it with the standard OpenWRT flash layout
You can find this in the DTS files for the Omega2 devices:
General Omega2: https://github.com/OnionIoT/source/blob/openwrt-18.06/target/linux/ramips/dts/OMEGA2.dtsi
Omega2/Omega2S specific: https://github.com/OnionIoT/source/blob/openwrt-18.06/target/linux/ramips/dts/OMEGA2.dts
Omega2+/Omega2S+ specific: https://github.com/OnionIoT/source/blob/openwrt-18.06/target/linux/ramips/dts/OMEGA2P.dts
Here's how you would read it:
So it would be like this:
u-boot: 192kb
u-boot-env: 64kb
factory: 64kb
firmware: remainder of flash
Hi @naveen_kumar ,
Any success on dialing up connection on EC200U-CN?
I have found a application note mentioning use of modem manager for EC200U-CN
reference: EC200U-CN dial up
try installing network-manager modemmanager and libqmi-utils udhcpc, ignore these packages if already installed
or try using EC200 in ECM/RNDIS mode by configuring through at command AT+QCFG="usbnet"[,<net>], where net =1 is for ECM mode and 3 for RNDIS
I was looking back at this for a project again. I was able to get the firmware updated. Watch out for 15.05 though, OpenSSL isn't installed on that so I couldn't use OPKG. Otherwise, I now have an up to date Onion! Thanks folks!
@SpiderKenny You can use sshpass, here's my rough notes on how to use it to deploy firmware using scp and ssh with sshpass:
// using sshpass to deploy new firmware
ssh-keygen -f "/home/chris/.ssh/known_hosts" -R "fe80::42a3:6bff:fec3:cb5b%enp0s31f6"
sshpass -ponioneer scp -6 -o StrictHostKeyChecking=no ~/source/bin/targets/ramips/mt76x8/openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin root@[fe80::42a3:6bff:fec3:cb5b%enp0s31f6]:/tmp
sshpass -ponioneer ssh -6 -o StrictHostKeyChecking=no root@fe80::42a3:6bff:fec3:cb5b%enp0s31f6 sysupgrade -n /tmp/openwrt-ramips-mt76x8-omega2p-squashfs-sysupgrade.bin
fe80::42a3:6bff:fec3:cb5b
@SpiderKenny Yes fastgpio is better but I showed code that uses the file system instead as I'm not sure of your level of experience and this method is easy to implement.
@Alfonso-Blanco sh needs to be running indefinitely in the background. The command you need is probably something like sh > /dev/tty0 &
More info on running commands in the background here.
I recommend playing around with this just on the command line to get it working. Then once you've figured it out, you can add it to the rc.local so it runs at boot