@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: Cant Start the Camera in Sudden
-
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!
-
RE: Omega 2S+ Image Size
@matiaslao Ah looks like there's a typo in the Omega2 Pro device tree specification file. That's why the build system thinks only 16MB are available.
We'll look into fixing that and will let you know!
-
RE: Omega 2S+ Image Size
Agree with @crispyoz, this line in the warning message spells it out:
WARNING: Image file /home/lyrtron-dev/onion/source/build_dir/target-mipsel_24kc_musl/linux-ramips_mt76x8/tmp/openwrt-ramips-mt76x8-omega2pro-squashfs-sysupgrade.bin is too big
-
RE: Omega Dash Display Part Number or Controller
@Alfonso-Blanco
sh
needs to be running indefinitely in the background. The command you need is probably something likesh > /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 -
RE: Omega 2S+ Image Size
@matiaslao what method are you using to create the custom image?
Please also share the error message you're seeing. -
RE: Omega Dash Display Part Number or Controller
@Alfonso-Blanco Yes, it will only work on an Omega2+
The Omega2 Dash is based on the Omega2S+ which has the same amount of RAM and Storage as the Omega2+