The USB pins exposed on the expansion header are the same USB signals that are routed to the USB-A Host Port. You can use one or the other at one time, but not both.
You can see this in the Omega2 Pro schematic. The same nets are connected to the USB host port and the expansion header:
@Nomadic-Homebody please don't resurrect 8 year old posts or have several posts about the same issue. Please stick to your original thread.
This thread doesn't apply to your situation since you're on the beta firmware that was introduced this year (2023). This thread is about the original Omega, from before the Omega2
@justRobsi this sounds like a power issue. When installing packages the wifi radio is working to download the files, the CPU is writing the download to RAM, etc. There's a lot going on so the power draw increases significantly and sharply.
To get over this hurdle during development, I recommend either:
Using an Omega2S Development Kit - it allows for swapping Omega2S modules and has the required power circuit
Getting a (through-hole) Omega2 or Omega2+ and a Dock for your development - this will eliminate any power supply issues
And then when making your own circuit to power the Omega2S, please refer to the Omega2S Hardware Design Guide and the Omega2S reference schematic
Tested with a jack 3.5 to USB adapter + headset with microphone and jack 3.5 connection: it works much better. Some background noise can be listened, but nothing very important.
I suppose, with the right headset, sound would be event much better.
@mohamedkallel the wifi radio calibration stored in the factory partition is unique to each device. It's done in the factory as part of QA testing with the help of an RF calibration machine. We do not recommend changing these values.
Hence we do not recommend using a flash programmer to write complete images to the flash.
It's possible to use a flash programmer (external hardware) to write all of the partitions to the flash storage at once.
First, create the image: use the flash programmer to read and create a binary image of an Omega2 that's setup how you want it,
Then, write the image to other devices: use the flash programmer to write the image to other Omega2 devices.
This is similar to the cloning process described in the FAQs.
The key differences are:
Use Linux to create partition image
Use a flash programmer (external) hardware to create an image of the flash
Clones only the overlay partition
Duplicates all partitions on the flash
We recommend against using a flash programmer to write complete images to the flash.
For one thing, the factory (aka art) partition holds wifi radio configuration and MAC addresses that are programmed at the factory and are unique to each device.
If the factory partition is overwritten, you will need to boot the device (either into the bootloader or Linux) to, at minimum, write unique MAC addresses to the factory partition.
If you're already booting into Linux, then it makes sense to use the sysupgrade command to install a firmware image as @JeffZhou mentioned above.
This process will only update the firmware and kernel partitions, leaving the bootloader and factory partitions as they are.
As a second option, in case this isn't helpful since you need to "clone" the firmware setup of a device, we recommend looking at this FAQ post: https://community.onion.io/topic/4563/faq-is-it-possible-to-clone-the-firmware-running-on-an-omega2-device-and-copy-it-to-other-omega2-units
It doesn't overwrite the factory partition, but there are other trade-offs.
@DocHardinger Both SPI and onewire are still in the pipeline.
We're currently working on making device tree overlays loadable during run-time. More info on the progress of that here: https://github.com/OnionIoT/OpenWRT-Packages/issues/62
We'll need the device tree overlay functionality to make one-wire work - as a lot of the "custom" gpio modules were removed from the linux kernel. @luz posted above in this thread with more details.
TL;DR: we're still working on improving the beta firmware. Expect SPI and one-wire to be completed in the coming weeks.
Looks like your connection to Community was lost, please wait while we try to reconnect.