@Moonshiner how many Omega2 units are exhibiting this issue?
I think the next step would be to identify if it's an issue with the Omega itself or something to do with the custom hardware.
Can you try putting these same units into Onion hardware and trying the same thing?
If you're using the Omega2/Omega2+, you can use any of the Docks.
If you're using the Omega2S/Omega2S+, you can use the Omega2S Dev Kit.
Let me know how it goes
We'll be launching the Onion Tau LiDAR Camera, the first in a new product line, in the coming weeks!
The Tau Camera is a 3D depth camera. Think of it like a regular webcam, except that it produces 3D depth data instead of color frames. It's an affordable next step beyond single-point depth or one-dimensional scanner solutions, and serves as a great starting point for 3D depth sensing.
It will be bundled with an open-source web app for visualizing the 3D data, as well as an OpenCV-compatible and open-source Python API for building your own applications.
It will be launching on Crowd Supply and shipping in spring 2021.
We've made this new Community Category as a place to talk about anything related to the Tau Camera. Welcome and enjoy!
@Waqas yeah it looks like vscode is trying compile on the Omega2 and its compiler doesn't have support for MIPS processors and/or OpenWRT
I assume this is C or C++ code?
Here are a some resources for working with C/C++:
@Moonshiner It would help to know what product you're using.
For Omega2, Omega2+, Omega2S, or Omega2S+, please provide some details about the carrier board being used. Is it an Omega2S Dev Kit, an Omega2 Dock, or is it custom hardware?
More info on best practises for asking for help here: https://community.onion.io/topic/4209/how-to-ask-for-help-on-this-forum
@Waqas The default shell is actually ash - a lightweight version of the unix shell - in order to conserve space.
root@Omega-F195:/# echo $0
/bin/ash
It looks like Visual Studio depends on having bash available. You can install it using the package manager:
opkg update
opkg install bash
Wanted to chime in here: the latest version of the bootloader fixes the USB flashing method!
All of the relevant info can be found here: https://community.onion.io/topic/4132/bootloader-update-fix-for-flashing-firmware-from-usb-storage
Just note that you'll need to use the Web Recovery method to update the bootloader. Might be easiest to get your hands on an ethernet expansion.
Check out the OpenWRT documentation on this topic: https://openwrt.org/docs/techref/hardware/port.i2c#i2c_over_gpio
Install the required kernel modules
opkg update
opkg install kmod-i2c-gpio-custom
Setup a bus:
insmod i2c-gpio-custom bus<BUS NUMBER>=<BUS NUMBER>,<SDA GPIO>,<SCL GPIO>
For example, to setup a SW I2C bus with SDA on GPIO18 and SCL on GPIO19:
insmod i2c-gpio-custom bus1=1,18,19
If all goes well, there will be a message in the kernel log:
[ 308.931002] Custom GPIO-based I2C driver version 0.1.1
[ 308.936785] i2c-gpio i2c-gpio.1: using pins 18 (SDA) and 19 (SCL)
And there will be a new I2C bus 1 device available:
root@Omega-F195:/# ls /dev/i2c-*
/dev/i2c-0 /dev/i2c-1
bus0 label, so your new sw i2c bus will need to be bus1latest available firmware to install the required kernel modules. See our documentation for more details.If you are using SW I2C over GPIO, then when you insert the kernel module you can specify a delay value
For example:
insmod i2c-gpio-custom bus1=1,5,4,udelay
where I2C speed (kHz) = 500 / udelay
udelay can only be an integer
Keep in mind this is bit banging so the timing is not exact however since I2C is synchronous it should not be a problem.
The hardware I2C bus on the Omega2 family has a default clock speed of 100kHz, the standard clock speed for I2C:
The clock speed is governed by the clock divider in the I2C SM0CTL0 register.
The register's default value is 0x8190 800F, with 0x190 set for the clock divider.
It is possible to change the I2C bus clock speed to 400kHz (fast mode) by writing to the SM0CTL0 register using devmem to change the clock divider:
devmem 0x10000940 32 0x8064800F
This changes the clock divider to
0x64(100), 40MHz / 100 = 400 kHz
To optionally confirm, read the register:
devmem 0x10000940
0x8064800F
Tested on firmware v0.3.2
Credit goes to @György-Farkas from this post from 2018.
Check out the MT7688 SoC datasheet to see the full register definition.
@crispyoz good idea! made an FAQ here: https://community.onion.io/topic/4321/faq-any-tips-for-designing-custom-hardware-that-uses-the-omega2s
we'll also make a blog post about it on the onion site. any other ways you can think of for getting the word out?
@jcoon said in SMS on Omega LTE:
I figured SMS would be possible via AT commands.
Yes, definitely doable!
@jcoon said in SMS on Omega LTE:
Making and answering calls should also be possible with AT commands. Is the hardware (microphone and speaker ports) capable of interfacing with the modem?
Like I said, we designed it with using the modem's cellular data functionality in mind. So the modem's audio interface isn't connected to the Omega. See the Omega2 LTE schematics for more details.
But it might be possible to get audio data over USB - not sure though, you'll have to do some exploration!
@josh-hightower should be able to edit the first post and change the title. lemme know if you can't
Yes, lots!
We recommend starting early development prototyping with the Omega2S Development Kit.
And then check out these resources for moving to your own custom hardware:
We welcome feedback on all documents! Please let us know in the forum or by posting an issue on Github
@Carey-Capaldi Awesome work! You should submit this to our Field Report contest with Crowd Supply and potentially win yourself some hardware as a prize!
@akif-durmaz Check out our new Omega2S hardware design guide, there's a section on ethernet design!
https://github.com/OnionIoT/Omega2/blob/master/Documents/Omega2S Hardware Design Guide.pdf
@hc To expand on what @crispyoz said:
The firmware is open source under the GPLv2 license. According to the license, you will need to publish your customizations with the same license.
However, that doesn't preclude you from creating and including closed-source software packages in your firmware.
@jcoon the Omega2 LTE was primarily designed to use the modem's cellular data functionality, that's why the o2lte command doesn't have voice or sms options.
However, it's possible to use AT commands to communicate with the modem and send sms messages. Try looking up Quectel's AT command guides for the EC25 and EG25-G
Can I ask why voice/sms is preferable to using cellular data for the same thing?
@virajp Check out our new Omega2S hardware design guide, there's a USB Hub section!
https://github.com/OnionIoT/Omega2/blob/master/Documents/Omega2S Hardware Design Guide.pdf