@MK Omega2 uses NOR flash, there's a discussion here:
https://community.onion.io/topic/4987/enabling-reset-hack-on-boot?_=1714985949781
You can also check some of my posts for an image of the Omega without the top cover so you can see the actual chip.
Not sure about the specifics of the difference between du and df however all file systems waste space, as a simple example imagine your file requires 2.5bytes of data, ie 20bits, ie 2 full 8bit bytes and half the other byte, the 4 remaining bits of the 8 bit byte end up as slack on most file systems. Also consider JFSS etc mark bad bytes, so the actual capacity of the FLASH is less than specified. Not a definitive answer but pointers for further research.
Go-to resource for frequently asked technical questions
55
Topics
121
Posts
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
@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.