@Antony This is explained here in the documentation: https://docs.onion.io/omega2-docs/oled-expansion-python-module.html#oled-py-draw-from-file

@JeffZhou Thanks a lot, for your response! I think that the 2nd point (VCC current) was the root cause of my issues: I used an AWG30 wire for all VCC lines which was too thin to carry the current. Regarding the UART <-> USB-Bridge the issue still persists, it requires a little fiddling: opening the serial connection after counting to three after plugging in. Then it worked booted in 100% correctly so far. Best Regards!

@Russell-Pirie "...will they all fit??...." You'd need to be specific as to what they are and how they are configured in order to answer that. I'm not sure you need to rewrite a bluetooth driver, most users would utilise "Bluez" package for bluetooth, perhaps take a look at that package and see if it meets your requirements, here's a link to the package: https://openwrt.org/docs/guide-user/hardware/bluetooth/usb.bluetooth I flash my devices using a bash script (well ash), it just connects to the device(s) using ipv6, uploads the firmware and then ssh's into the device and execute the firmware upgrade. You could tweak my script a bit to make it handle multiple devices at once. I did about 40 of them today using my exiting script, one by one while I was eating lunch and watching the news. My script is here: https://community.onion.io/topic/4483/script-to-deploy-firmware-to-device-using-ethernet-ipv6 The other option is to boot into u-boot and flash from USB.

@sscalf fill out the quote form and respond to the email that we send you!

@cspensky take a look at this tread. https://community.onion.io/topic/4330/unable-to-flash-firmware-from-usb/12?_=1612513950216 @tjoseph1 has a nice solution

I think I'm closer to the answer. It seems to lie in the register AGPIO_CFG at address 0x1000003C. It switches the GPIOs 14 through 29 between the digital pins and the analog ethernet counterparts. Would this modification to AGPIO be done in the DTSI file, some bootloader/kernel parameter or do I need to make a patch to something somewhere? I'm aware I could use something like devmem to directly set this register from userspace but I assume there is something a bit cleaner?

@jossvall The UART TXD0 and TXD1 pins fall into the "must be floating or pulled down at boot time" category. That should be satisfied by most UART devices. Excerpt from the Omega2S Datasheet:

@supczinskib Kewl. Glad to see you are making progress. I continue to watch with interest.

@luz How to detect... "locally"? It is fairly easy since there is an Onion Omega2+ / Onion Omega2 sticker on the device If you don't believe the sticker a reboot command and the bootloader messages on the Serial Console can help. For example - please watch the 'find flash: ' line: # HW Omega2+ # FW v0.3.2 b240 # http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2-v0.3.2-b240.bin # U-Boot 1.1.3 (Oct 18 2016 - 17:29:05) root@Omega-5BE1:/# reboot ____ _ ____ / __ \___ (_)__ ___ / __ \__ _ ___ ___ ____ _ / /_/ / _ \/ / _ \/ _ \ / /_/ / ' \/ -_) _ `/ _ `/ \____/_//_/_/\___/_//_/ \____/_/_/_/\__/\_, /\_,_/ W H A T W I L L Y O U I N V E N T ? /___/" Board: Onion Omega2 APSoC DRAM: 128 MB relocate_code Pointer at: 87f60000 ****************************** Software System Reset Occurred ****************************** flash manufacture id: c2, device id 20 19 find flash: MX25L25635E ============================================ Onion Omega2 UBoot Version: 4.3.0.3 --- root@Omega-5BE1:/# ubus call system board { "kernel": "4.14.81", "hostname": "Omega-5BE1", "system": "MediaTek MT7688 ver:1 eco:2", "model": "Onion Omega2", "board_name": "omega2", "release": { "distribution": "OpenWrt", "version": "18.06-SNAPSHOT", "revision": "r0+7471-90181760c3", "target": "ramips\/mt76x8", "description": "OpenWrt 18.06-SNAPSHOT r0+7471-90181760c3" } } # HW Omega2+ # FW v0.3.2 b240 # http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2p-v0.3.2-b240.bin # U-Boot 1.1.3 (Oct 18 2016 - 17:29:05) root@Omega-5BE1:/# reboot ____ _ ____ / __ \___ (_)__ ___ / __ \__ _ ___ ___ ____ _ / /_/ / _ \/ / _ \/ _ \ / /_/ / ' \/ -_) _ `/ _ `/ \____/_//_/_/\___/_//_/ \____/_/_/_/\__/\_, /\_,_/ W H A T W I L L Y O U I N V E N T ? /___/" Board: Onion Omega2 APSoC DRAM: 128 MB relocate_code Pointer at: 87f60000 ****************************** Software System Reset Occurred ****************************** flash manufacture id: c2, device id 20 19 find flash: MX25L25635E ============================================ Onion Omega2 UBoot Version: 4.3.0.3 --- root@Omega-5BE1:/# ubus call system board { "kernel": "4.14.81", "hostname": "Omega-5BE1", "system": "MediaTek MT7688 ver:1 eco:2", "model": "Onion Omega2+", "board_name": "omega2p", "release": { "distribution": "OpenWrt", "version": "18.06-SNAPSHOT", "revision": "r0+7471-90181760c3", "target": "ramips\/mt76x8", "description": "OpenWrt 18.06-SNAPSHOT r0+7471-90181760c3" } } # HW Omega2 # FW v0.3.2 b240 # http://repo.onioniot.com.s3.amazonaws.com/omega2/images/omega2-v0.3.2-b240.bin # U-Boot 1.1.3 (Oct 18 2016 - 17:30:55) root@Omega-5533:/# reboot ____ _ ____ / __ \___ (_)__ ___ / __ \__ _ ___ ___ ____ _ / /_/ / _ \/ / _ \/ _ \ / /_/ / ' \/ -_) _ `/ _ `/ \____/_//_/_/\___/_//_/ \____/_/_/_/\__/\_, /\_,_/ W H A T W I L L Y O U I N V E N T ? /___/" Board: Onion Omega2 APSoC DRAM: 64 MB relocate_code Pointer at: 83f60000 flash manufacture id: ef, device id 40 18 find flash: W25Q128BV ============================================ Onion Omega2 UBoot Version: 4.3.0.3 --- root@Omega-5533:/# ubus call system board { "kernel": "4.14.81", "hostname": "Omega-5533", "system": "MediaTek MT7688 ver:1 eco:2", "model": "Onion Omega2", "board_name": "omega2", "release": { "distribution": "OpenWrt", "version": "18.06-SNAPSHOT", "revision": "r0+7471-90181760c3", "target": "ramips\/mt76x8", "description": "OpenWrt 18.06-SNAPSHOT r0+7471-90181760c3" } } How to detect... "remotely"? That is the question.

Your information is very interesting. Thank you for sharing

Thanks @György-Farkas and @crispyoz for the confirmation. I have seen the 2S reference but just wanted to make sure before I spin out a PCB as there is a discrepancy with the 2/+.

Thanks will certainly consider the chip option. I'll also try and copy the trace antenna from the dev board image as best as possible and compare results.

When powered directly, without the dev board, power consumption is as expected 141mA@3V3 when idling with WiFi off.

That worked. Thanks so much.

@Lazar-Demin @György-Farkas thanks, I was starting to think I was stupid. This explains some inconsistent outcomes I was experiencing.

readValue needs to be passed as a reference, since the contents will be modified by the i2c_read function. That's likely causing the segmentation fault. Or change readValue to a point and allocate two bytes before passing it to i2c_read See the documentation for the i2c_read function for more details: http://docs.onion.io/omega2-docs/i2c-c-library.html#i2c-c-read-multiple-bytes

@Don-Elwell I've wondered about the same thing when thinking about an Omega2(S) with a PCIe graphics card Let me know if you find out something..