@CAP-33 what firmware are you running? Here's what I see on a device on v0.3.2 b232:
# ls /dev/gpio*
/dev/gpiochip0 /dev/gpiochip1 /dev/gpiochip2
We've generally used the sysfs gpio interface: https://www.kernel.org/doc/html/latest/admin-guide/gpio/sysfs.html
But I've just learned that sysfs has been deprecated since linux 4.8 and that descriptor-based access (through /dev/gpiochipN) is the new way to go (see article here) ...
@cmelnick It's possible the onion-i2c:: debug readings aren't 100% correct.
Can you try changing your code when you read to this:
val = i2c.readBytes(0x5a, 0x5d, 1)
print(val)
@György-Farkas said in emmc 8GB disabled:
Is it possible to install any packages with opkg to an eMMC external storage (without pivot overlay, extroot, Omega2 Pro FW of course)?
It is possible, but looks like it might take some additional work: https://openwrt.org/docs/guide-user/additional-software/opkg#non-standard_installation_destinations
@Nagarjuna-Reddy said in emmc 8GB disabled:
@György-Farkas
can you please explain clearly because I have not understood.
/usr/bin/o2-pro-init only applies if you're running Omega2 Pro firmware.
You can ignore this if you're running the default Omega2+ firmware. Which you likely are.
@Nagarjuna-Reddy just to confirm, you're using the Omega2S Development Kit with 8 GB eMMC?
With the default firmware on your Omega2S+, all of the packages and changes you make to the filesystem will be on the internal flash.
The eMMC storage is just external storage that's mounted automatically. No changes are made to this filesystem unless you specifically go to /mnt/mmmcblk0p1 and make changes there.
You can manually unmount it by running umount /mnt/mmcblk0p1
Btw, the automatic mounting is handled by the fstab utility. Read more about it here
And to answer your questions:
what is this
tmpfs is a temporary filesystem running on the RAM. This is a function of OpenWRT. Learn more here: https://openwrt.org/docs/techref/file_system
why my flash memory it is showing very less MB. but we have 32MB flash memory.
The internal flash memory is 32MB. You're not seeing the full 32MB because of how the flash is partitioned. Learn more about that here:
Note: the examples given in the links above don't match 1-to-1 with the Omega2, but they will illustrate the principle
@user5456 How are you powering your device? Through USB on a Dock?
@Nagarjuna-Reddy tmpfs is a temporary filesystem running on the RAM. So that won't help in this case.
Like we mention in the FAQ: Use the Omega2+/2S+ during development for the most flexibility. If and when you start thinking about production, you'll have a better idea of your storage and memory requirements, and can choose between the 2 and 2+ variants.
Btw, this topic looks like a duplicate to https://community.onion.io/topic/4058/onion-omega2s-memory-issue/
Please keep the discussion of a single topic in one thread - otherwise the forum will get bloated with duplicate threads.
@Nagarjuna-Reddy python is a pretty large package
See this FAQ: https://community.onion.io/topic/4063/faq-what-if-my-device-runs-out-of-storage-space
Added an FAQ to cover this topic (installing packages from the openwrt package repos)
https://community.onion.io/topic/4066/faq-how-do-i-install-_____-package
By default, the opkg package manager on the Omega2 platform is configured use Onion’s online package repositories. We host a selection of packages that are frequently used by the Omega2 userbase. However, the official OpenWRT repositories host a larger selection of packages.
If you’re looking for a specific package and it isn’t available by default, you can try enabling the official OpenWRT package repositories on your Omega.
Learn more here: http://docs.onion.io/omega2-docs/using-opkg.html#you-dont-have-a-package-i-wantneed
The Omega2/2S comes with 16MB of internal flash storage, while the Omega2+/2S+ come with 32MB.
Storage is used by installed packages and adding files to the filesystem.
It's definitely possible to fill up all of the available storage on your device.
You can tell if you get a message like this when trying to install a package:
Or if you run the df command and find the /overlay partition is full:
If you've installed a lot of packages, you can remove installed packages you no longer need. List out installed packages with with opkg list-installed, and use opkg remove to uninstall ones that you no longer need.
Note that uninstalling packages that came bundled with the firmware (as part of rootfs) will not result in freed space. This is due to how the OpenWRT partitioning works - see more on that here: https://openwrt.org/docs/techref/flash.layout
Alternatively, you can perform a factory restore and start fresh with this device. Just note that performing a Factory Restore on your Omega will revert all files to the default for the currently installed firmware, all other files will be deleted. More on that here: http://docs.onion.io/omega2-docs/factory-reset.html
If you find that you need more than the 32MB offered by the Omega2+/2S+:
If you're building your own custom hardware and need more than 32MB, consider including an SD card slot or eMMC storage in your design.
Use the Omega2+/2S+ during development for the most flexibility. If and when you start thinking about production, you'll have a better idea of your storage and memory requirements, and can choose between the 2 and 2+ variants.
@Victor-Lucio The RootCA is a certificate that you can download from Amazon.
See these resources:
https://docs.aws.amazon.com/iot/latest/developerguide/create-device-certificate.html
https://onion.io/2bt-aws-iot-setup-single-command/
On March 2, 2020, the Onion Community Forum underwent routine maintenance. As part of the maintenance, the forum user system was updated - requiring all users to reset their password.
You can easily reset your password if your profile has an up-to-date email address:
Be patient waiting for the email, we anticipate a lot of users requesting password resets at the same time. It may take up to half an hour to be sent out.
Also, check your spam folder for the password reset email!
If you still can't reset your password, you have two options:
Please make sure to mention that:
We'll do our best to help you out. This may result in an influx of tickets, so we may be delayed in our response.
Community maintenance is now complete! You will need to reset your password before logging in
Added DXF measurement files for the Omega2 Pro, Omega2 LTE, and Omega2 Dash to their respective repos:
You can get super precise measurements from these files. Onshape is a decent, free online service you can use to view the files.
The news is true, Onion is discontinuing the following products:
They will continue to be sold on the Onion store and by other retailers until inventory runs out.
Blog post here: https://onion.io/discontinuing-3-expansion-and-a-kit/
If you're experiencing this same issue in 2020, read on:
This kernel panic issue was caused by the WiFi driver used in firmware versions 0.1.x
Upgrading the Omega's firmware will resolve this issue.
All firmware released March 2018 and later (version 0.2.0 and up) use a completely overhauled and much more stable wifi driver.
Use the bootloader and web recovery mode to install the latest firmware. See this guide for more details: http://docs.onion.io/omega2-docs/Firmware-Flashing-Web-Recovery.html
@György-Farkas I did mention it previously:
@Lazar-Demin said in Contradiction in Omega2 Device MAC Address Allocation:
Earlier in the production lifetime of the Omega2 we used to write the MAC addresses like what you're seeing:
But I had to confirm the timing of the change 
There's no advantages to one schema or the other. Remember that both schemas will work just fine.
We just chose to standardize to the one mentioned in the docs article.
@György-Farkas said in Contradiction in Omega2 Device MAC Address Allocation:
Does this mean that a FW sysupgrade is not enough?
A firmware sysupgrade will not touch the factory partition! So no, it will not fix the the addressing schema
@György-Farkas said in Contradiction in Omega2 Device MAC Address Allocation:
Can the workaround what you suggested in this post correct only the MAC address collision but can't not set the new addressing schema?
Are you referring to the uci set network.wan.macaddr= ... workaround? And setting the eth0 mac address to ra0 + 1?
The wifi driver will still read the apcli0 mac address from the factory partition at "The 6 bytes starting at 0x002e - the apcli0 MAC address".
So you will end up with a collision.
The last post in that topic mentions we put out a Warp Core wifi driver fix for address duplication.
With this fix, the apcli0 address will always be the 6 bytes starting at 0x002e from the factory partition.
And the eth0 address will always be the 6 bytes starting at 0x0028 from the factory partition. (This was true before the warp core update).
No matter how the MAC addresses were allocated in the factory, your device will work 100% normally.
As long as you're on firmware 0.3.x you will not have any collision issues and all three interfaces will have unique mac addresses.
If your device was manufactured before mid 2018, then it will not follow the mac address allocation schema that's published in our docs:
Instead eth0 mac address will be ra0 + 2
and apcli0 mac address will be ra0 + 1
However this will not cause any issues and your device will operate 100% normally
If your device was manufactured after mid 2018, the Mac addresses will follow the schema.
Like I mentioned, the factory partition is writeable. So it's possible to edit the factory partition to adjust the two mac addresses.
Here are the steps in broad strokes. I haven't tested these so proceed at your own risk
xxd packagexxd /dev/mtd2 > factory.hexxxd -r factory-new.hex > factory.binmtd -r write factory.bin factory