Why is SPI so broken? I know pulling some pins high will stop the Omega from booting but is it more than that ?
Thanks for the link I'll check it out.
I have been given one of these Waveshare 4.2 Inch e-paper module and wonder if anyone has had any experience at trying to get them to work with an Omega?
It supports a variety of platforms like RPi Arduno and STM32 and uses a SPI interface.
Python and C libs are available for the Pi and are GPL2
Any thoughts ?
Well the main issue I have with onion builds is the keep slipping behind the LEDE tree and so you end up with mismatched kernels constantly meaning rolling in driver changes is next to impossible unless you are building the firmware yourself, which brings up back to the point about reproducible builds because if we cannot build what onion builds then how can we update it to make custom builds?
In some respects I really wish Onion would just decide to track LEDE completely and upstream any custom changes that need to be made for a particular devices. As it stands now though I am terrified to do any sort of update on my omegas because there is a high probability it will break something. Even just being able to upgrade the kernel as a package would go a long way to making building for a target easier.
So tried this on both Onion2s I have. I thought maybe I had accidentally set one up myself at some point and forgotten but no, a brand new one out of the box has encryption turned on. I don't recall this being the same for the Omega 1 or for the Omega 2+. Am I missing something ?
-- CUT --
BSS 40:a3:6b:c0:a8:43(on wlp4s0) last seen: 49899.267s [boottime] TSF: 571974687 usec (0d, 00:09:31) freq: 2462 beacon interval: 100 TUs capability: ESS Privacy ShortSlotTime (0x0411) signal: -60.00 dBm last seen: 88 ms ago Information elements from Probe Response frame: SSID: Omega-A843 Supported rates: 1.0* 2.0* 5.5* 11.0* 9.0 18.0 36.0 54.0 DS Parameter set: channel 11 ERP: Barker_Preamble_Mode Extended supported rates: 6.0 12.0 24.0 48.0 HT capabilities: Capabilities: 0x2c HT20 SM Power Save disabled RX HT20 SGI No RX STBC Max AMSDU length: 3839 bytes No DSSS/CCK HT40 Maximum RX AMPDU length 65535 bytes (exponent: 0x003) Minimum RX AMPDU time spacing: 4 usec (0x05) HT RX MCS rate indexes supported: 0-7 HT TX MCS rate indexes are undefined HT operation: * primary channel: 11 * secondary channel offset: no secondary * STA channel width: 20 MHz * RIFS: 0 * HT protection: no * non-GF present: 0 * OBSS non-GF present: 0 * dual beacon: 0 * dual CTS protection: 0 * STBC beacon: 0 * L-SIG TXOP Prot: 0 * PCO active: 0 * PCO phase: 0 RSN: * Version: 1 * Group cipher: TKIP * Pairwise ciphers: TKIP CCMP * Authentication suites: PSK * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000) Extended capabilities: WMM: * Parameter version 1 * BE: CW 15-1023, AIFSN 3 * BK: CW 15-1023, AIFSN 7 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec * VO: CW 3-7, AIFSN 2, TXOP 1504 usec Country: US Environment: Indoor/Outdoor Channels [1 - 11] @ 16 dBm
Meh... you're right.. Missed that. Still no overly impressed to be honest but at least it is omega connected.
Well looks like another 2 bogus project been backed by Onion. A luxury 'Smartwatch' Which is in fact neither smart not luxury and a 'Smart Alram Clock' Which basically looks like an android phone in a non-phone case.
Really gotta wonder what the hell is going on and I am liable to stop following Onion in the future, despite how much I love the Omega. They are really starting to nark me off with their seemingly randomly backed projects.
Actually the router was the only one that piqued my interest but I still think it is a very niche project. It is not like you will be routing out PCB's or drilling them any time soon with that device, so not really very interested.
The love box is just plain silly. It is a kitsch to say the least and seems like a AWFULLY big box for something the omega could do even without customisation.
The Robot arm, frack me how anyone can think that is practical let alone useful. Are you really going to try and print on a non-flat non-heated non-enclosed surface and not get crappy prints?
The LED light kit? Really? How does that make anything easier? I guess again it is for a very niche market.
The wooden animals, Meh, cute but kinda retro but not in a good way. And this need to tout about FCS certification bugs me. FSC have had issues and I am not really sure they are legit anymore.
But that one that >really< grinds my gears is the Luna Scale. I have not seen such corporate flim flam for a long time. The go through an entire 5 min video complete with cheesy execs and fail to actually explain how their scale works and what makes it so much better than any other bluetooth scale. FFS!
I don't want to be that guy but by Onion backing such trash really is starting to change my perspective of the whole organisation.
Are you guys trying to write off you tax year or something?
7 projects in less than an hour some of which are particularly nonsensical seems a little excessive.
I know it is your business who you back but really when you do it all at once it makes a mess of my activity feed.
So what gives?
What do you get when you run
i2cdetect -y 0
It should give you a list of devices and their addresses like so:
0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 31 32 33 34 35 36 37 -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Identify the ones you know are connected and the one you cannot identify will be the RTC. If you are thinking the Omega has an RTC built in, then you are mistaken. You would need to hook one up to the i2c bus to be able to use one.
Sadly although the Kmod is in LEDE repos the kernel version is WAY ahead of the onion one now.
opkg install kmod-fs-f2fs
Installing kmod-fs-f2fs (4.9.34-1) to root...
- satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-f2fs:
- kernel (= 4.9.34-1-03997cbe2f6251de7784529eabe01f20) * kernel (= 4.9.34-1-03997cbe2f6251de7784529eabe01f20) *
- opkg_install_cmd: Cannot install package kmod-fs-f2fs.
Linux version 4.4.46 (root@2272a3272872) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3273-a0888ec) ) #0 Thu Feb 2 23:46:03 2017
So once again the not tracking of the LEDE repos leads to a version mismatch making it impossible to install kernel modules.
Unless the b163 build is more up to date, maybe I should just manually flash the LEDE build image from
Either way I want to be able to use f2fs because it is the 3rd time an SDcard with ext4 has started fritzing out on me.
do you mean that GPIOX (as in python code) is controlling the GPIOX (as shown on dock)?
I mean the electrical traces seem to be identical so where the GPIO pins are listed in the 2 dock they are actually still on the 1 dock. Just the names have changed. Basically I did not have to change the dock because I could still use the same GPIO pins as if it was a 2 dock but taking into account the gotcha of using GPIO pins 1 6 7 8 and 45 as per the annotated pinout otherwise the Omega might not boot.
Handy. The hardware is built now and works fine just need to concentrate on the software.
Looks like your connection to Onion Community was lost, please wait while we try to reconnect.