@crispyoz which firmware has this in customfeeds.conf?
-
RE: ⭐️ Beta OpenWRT 22.03 firmware available! Your feedback is needed ⭐️
-
RE: How quickly can I get I2C going during boot? (OLED DIsplay)
@SpiderKenny another option would be to modify the bootloader so it writes a loading screen to the OLED display before Linux even starts booting.
Might be a little work intensive tho! -
RE: ⭐️ Beta OpenWRT 22.03 firmware available! Your feedback is needed ⭐️
@crispyoz Yep, there are no beta firmware images for the Omega2 Pro, LTE or Dash.
We added Omega2 LTE support through a package - see https://documentation.onioniot.com/hardware-interfaces/omega2-lte
The v0.3.4 Omega2 Pro firmware just automated the booting from external storage and swap file procedure. Let us know if that would be helpful as a package available for the new firmware by submitting a "feature request" issue on github
-
RE: Onion Memory structure
@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
-
RE: Omega and capacitive touch screen
@MK This is awesome!! Great work!!
I'm curious, you said in Omega and capacitive touch screen:
All the static data (images, fixed texts, screen layout etc....) is not stored on the controller. The controller accesses this data on an external MicroSD card.
This MicroSD card is accessed only by the display controller and not the Omega2S?
-
RE: Cant Start the Camera in Sudden
@cyberai pls try running the
checkCamera.py
Example Python Program and posting the command line output and screenshots of the output.
This will give us a better idea of what's going on. -
RE: FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?
Ah I think this answers the question of why it doesn't work initially:
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:The woraround i found now is to first
sysupgrade -F -n -v onion_omega2p-22.03.5-20240122.bin a fresh omega
let that reboot and then
mtd -r write pan230_v4.1-96_20240222.bin firmware
This works, taking a LOT of precious extra time, but no nastyness.The target device needs to be running the same firmware version as the original device. (This is mentioned in Step 2 in the original post)
The reason being the cloning only overwrites the
firmware
partition. If the rest of the partitions don't match, that opens to door to the nastiness you've been experiencing.
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
thanks for that little push toward the image builder.
Glad you're finding it useful!!
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
I hope i still can bother you now and then, because i'm absolutely convinced i will find plenty of obstacles to be conquered
On that note, would it be better to report in the git issues or to discuss in the community?Definitely! Always open to suggestions!
I think the community is good for general discussion, if there's something specific then open a github issue
-
RE: FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?
Hey @tony-ter-neuzen, good to hear from you!
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
However during the write on a fresh Omega2S+ things get really nasty.
It's a strange error message, I haven't encountered it before.
Was this the first time you tried cloning to a fresh device? Were you able to get it to work before this?
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
after a very messy reboot a second firmware write with the same image makes everything good again
To make it good again did you reflash the beta firmware or write the cloned partition again?
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
I noticed that with an openwrt.bin you advise using sysupgrade -F -n -v <SELECTED-FIRMWARE-IMAGE>.bin (in your technical doc )
I am not sure if i can use sysupgrade to write our clone, but my guess is no. (NOOOH!)Your guess is correct, sysupgrade can only be used with full firmware images, it doesn't work with clone partition images
@tony-ter-neuzen said in FAQ: Is it possible to "clone" the firmware running on an Omega2 device and copy it to other Omega2 units?:
i'm also looking at how the openwrt-imagebuilder-wrapper works, maybe thats a better path... but it will take me a long while to migrate everything we have in that direction i'm afraid.
Do you think that's the way to go in this case?Yes, we made the openwrt-imagebuilder-wrapper for exactly this purpose
It's very simple to set up and incredibly quick to run - it takes minutes to build a firmware image. We use it to build our beta firmware and we plan on using this to move forward.So I definitely recommend moving in this direction.
The only wrinkle is that you'll need to have your customizations wrapped up as packages.
As a stop-gap, you can add individual files to the firmware build (see this section in the wrapper readme) but in the long-term we recommend having your custom programs, configs, etc in packages.If you have questions about the imagebuilder wrapper, feel free to post in the Omega2 Talk category and I'll get back to you!
-
RE: Omega 2S+ Image Size
@matiaslao the fix has been added to https://github.com/OnionIoT/source (and firmware v0.3.4 b258 has been released with this fix).
If you're working on with a local copy of the https://github.com/OnionIoT/source repo, you will need to do a pull to get the DTS changes.
If you've been compiling with this build system already, you'll also need to remove the
tmp
directory for the DTS changes to take effect (if I remember correctly)Let me know how it goes!