I could do with more documentation as well. I have no idea how to play audio from the command line on the Oboo clock. mpg123 is there and everything but there are no audio devices present. I have a sneaking feeling you need to use the mosquitto framework to use the audio but that is not terrible well documented and so not sure if I can do that from the command line easily.
So any central repository for docs would be helpful and know methods to access functions.
I am a UK user.. Does the same for me. A royal POA.
I really want some sort of dev guiide to be released because I want to customise or blank the cards when not in use as it just confuses the intended target. Plus I have a script I can use to auto dim the display when Daylight savings cut in.
Can we please have a devoted area to discuss such things ?
So I have just received my new Oboo Clock and wondering when we are going to open up a forum to discuss things about it. My main gripe atm is where is the developer access to it. SSH is not enabled by default and not sure what is the correct way to enable it.
Is there and SDK for the cards working with the bluetooth app etc..
Lots of questions come to mind.
Thanks.
Spam is on the increase via forums world wide it seems. But it is a case of active moderation and proper security practices. Sign ups need to be verified yes, but also activity needs to be monitors. Usually discourse handles it pretty well but in practice it requires a moderator to really fine grain things.
I am guessing the onion boys have too much else to do but looking after a community forum should really be left up to the community. A known good contributor and regular to the forums can be deputised to that end and at least fill in the gaps when the admins are away. Time zones are a pain regardless of the industry you are in so might be good to get multiple candidates from different areas of the world to help out.
Just a thought..
I noticed in my one the wifisetup script used uci set wireless.radio0.. when of course the device is actuall ra0 now.
That fixed that problem.. but still cannot get it to connect to any of my wifi AP's,
bizarre.
Ok so I flashed this to my OO2P and as I had nothing to lose also factory reset it with firstboot -y
So I was a little surprised when I say a segfault on restart to do with the SPI driver.
[ 11.542654] spidev spi32766.1: buggy DT: spidev listed directly in DT
[ 11.549271] ------------[ cut here ]------------
[ 11.553970] WARNING: CPU: 0 PID: 486 at drivers/spi/spidev.c:720 0x8768833c()
[ 11.561222] Modules linked in: spidev(+) snd_usbmidi_lib slhc rfcomm nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack iptable_mangle iptable_filter ip_tables hidp hid_generic hci_uart crc_ccitt cdc_acm btusb btintel bnep bluetooth snd_soc_simple_card snd_soc_ralink_i2s snd_soc_wm8960 videobuf2_vmalloc videobuf2_memops videobuf2_core hid v4l2_common videodev evdev snd_soc_core mt_wifi ralink_gdma virt_dma ledtrig_oneshot ledtrig_morse ledtrig_heartbeat ledtrig_gpio ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables msdos snd_pcm_dmaengine snd_compress snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_rawmidi snd_seq_device snd_hwdep snd input_core soundcore vfat fat ntfs configfs autofs4 nls_utf8 nls_iso8859_1 nls_cp437 regmap_i2c dma_shared_buffer ecb cmac mmc_block usb_storage sdhci_pltfm sdhci mtk_sd mmc_core leds_gpio ohci_platform ohci_hcd ledtrig_transient ehci_platform ehci_hcd sd_mod scsi_mod gpio_button_hotplug ext4 jbd2 mbcache exfat usbcore nls_base usb_common crc16 cryptomgr aead crypto_null crc32c_generic crypto_hash
[ 11.666647] CPU: 0 PID: 486 Comm: kmodloader Not tainted 4.4.74 #0
[ 11.672911] Stack : 80380780 00000000 00000001 803d0000 87dab4d4 803cae63 80361c18 000001e6
[ 11.672911] 80413438 0000000c 0000001a 024000c0 80066378 8004af58 80367120 803c0000
[ 11.672911] 00000003 0000000c 80365524 875a7b4c 80066378 80048ec4 00000000 00000000
[ 11.672911] 00000001 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.672911] 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 11.672911] ...
[ 11.709089] Call Trace:
[ 11.711629] [<80066378>] module_sect_show+0x0/0x18
[ 11.716513] [<8004af58>] vprintk_default+0x24/0x30
[ 11.721390] [<80066378>] module_sect_show+0x0/0x18
[ 11.726268] [<80048ec4>] printk+0x2c/0x38
[ 11.730352] [<8002552c>] warn_slowpath_common+0xa0/0xd0
[ 11.735683] [<8014de3c>] dump_stack+0x14/0x28
[ 11.740106] [<80014908>] show_stack+0x50/0x84
[ 11.744524] [<8002552c>] warn_slowpath_common+0xa0/0xd0
[ 11.749843] [<8768833c>] 0x8768833c
[ 11.753403] [<800255e4>] warn_slowpath_null+0x18/0x24
[ 11.758560] [<801fb304>] of_match_node+0x20/0x44
[ 11.763272] [<8768833c>] 0x8768833c
[ 11.766846] [<801c0a10>] devm_kfree+0x20/0x44
[ 11.771285] [<801e1bd8>] spi_drv_probe+0x3c/0x84
[ 11.775994] [<801bd540>] driver_probe_device+0x120/0x288
[ 11.781405] [<8008b928>] kstrdup+0x44/0x8c
[ 11.785589] [<801e1ad8>] spi_match_device+0x38/0xa8
[ 11.790567] [<801bd724>] __driver_attach+0x7c/0xb4
[ 11.795442] [<801bb948>] next_device+0x10/0x30
[ 11.799959] [<801bd6a8>] __driver_attach+0x0/0xb4
[ 11.804746] [<801bba04>] bus_for_each_dev+0x9c/0xac
[ 11.809706] [<80303c9c>] klist_add_tail+0x24/0x50
[ 11.814484] [<801bb7d8>] bus_get+0x2c/0x50
[ 11.818679] [<801bcc38>] bus_add_driver+0xec/0x20c
[ 11.823549] [<800ae92c>] exact_match+0x0/0x8
[ 11.827899] [<800aee34>] exact_lock+0x0/0x24
[ 11.832253] [<801bde3c>] driver_register+0xa8/0xf8
[ 11.837133] [<8775a000>] init_module+0x0/0xdc [spidev]
[ 11.842387] [<8775a098>] init_module+0x98/0xdc [spidev]
[ 11.847711] [<80159a08>] kasprintf+0x1c/0x28
[ 11.852061] [<800458b0>] __wake_up+0x24/0x48
[ 11.856412] [<8775a000>] init_module+0x0/0xdc [spidev]
[ 11.861646] [<8000d938>] do_one_initcall+0x1e8/0x214
[ 11.866709] [<800458b0>] __wake_up+0x24/0x48
[ 11.871046] [<8775a000>] init_module+0x0/0xdc [spidev]
[ 11.876291] [<80034568>] call_usermodehelper_exec+0x144/0x160
[ 11.882138] [<80034058>] call_usermodehelper_setup+0x38/0xa8
[ 11.887922] [<80066378>] module_sect_show+0x0/0x18
[ 11.892805] [<80067598>] do_init_module+0x74/0x1cc
[ 11.897700] [<8009f418>] __vunmap+0xf0/0x114
[ 11.902076] [<80068e2c>] load_module+0x16c0/0x1b68
[ 11.906958] [<80066964>] unknown_module_param_cb+0x0/0xac
[ 11.912443] [<8009f90c>] __vmalloc_node+0x34/0x40
[ 11.917260] [<80069368>] SyS_init_module+0x94/0x180
[ 11.922213] [<80069404>] SyS_init_module+0x130/0x180
[ 11.927293] [<8000682c>] syscall_common+0x30/0x54
[ 11.932077] [<80008c58>] __bzero+0xbc/0x164
[ 11.936331]
[ 11.937846] ---[ end trace d1d675f9648aa3a7 ]---
I was also surprised when the promised better performing 'Warp Core' driver did not seem connect to any of my networks. In fact it kept on saying it connected but there was no internet. A blatant falsehood given that my laptop I was using to login via the Serial console was working fine on the same access points.
Anyway of debugging what is going on? If i cannot connect to wifi then not sure how I will ever fix a problem on it again.
Install offical firmware:
the trouble with the official firmware and i have complained about this on numerous occasions is it does not track lede/openwrt properly. So the 2 things I want working on my omega are f2fs and tinc. Both of which cannot because the damn kernel version does not match up with any of the tools or packages.
It is for that reason I am using LEDE directly because it is impossible to use the stock firmware with standard packages.
Hey,
Been a few months since I played with my Omega and maybe I have forgotten something. I flashed the latest LEDE image ( 17.01.4) to the 2+ and it broadcasts fine on radio0 but I cannot recall what device I need to call to make it connect to an AP as well.
On the Onion build it is ra0
config wifi-device 'ra0'
option type 'ralink'
option mode '9'
option channel 'auto'
option txpower '100'
option ht '20'
option country 'US'
option disabled '0'
But there is no ra0 device in LEDE. In fact the only devices I see are these.
cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
eth0.1: 0 0 0 0 0 0 0 0 3240 20 0 0 0 0 0 0
lo: 142072 2184 0 0 0 0 0 0 142072 2184 0 0 0 0 0 0
wlan0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
eth0: 0 0 0 0 0 0 0 0 321263 953 0 0 0 0 0 0
br-wlan: 0 0 0 0 0 0 0 0 3240 20 0 0 0 0 0 0
eth0.2: 0 0 0 0 0 0 0 0 311766 917 0 0 0 0 0 0
So in theory wlan0 should be the device. but when I set it as that I get.
wifi
wlan0(): Interface type not supported
'radio0' is disabled
wlan0(): Interface type not supported
'radio0' is disabled
The wifi device is definitely found because it can be seen via iw.
iw list
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 1:
Capabilities: 0x1fe
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 1-stream
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 TX/RX MCS rate indexes supported: 0-15
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
valid interface combinations:
* #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 4,
total <= 4, #channels <= 1, STA/AP BI must match
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
So what am I missing here? Do I need to specify the device type to something (ie 'ralink' in the default firmware) in which case what should it be?
Any help appreciated.
Thanks.
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 ?
Thanks.
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.
Forget it. My bad.. of course the password is 12345678
Doh!... Can't believe I forgot that..
Amen to that.
If Debian are pushing to 100% reproducible builds I think LEDE should where it can and save some binary blobs which can be checksummed should have everything easily checked.
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 dBmMeh... you're right.. Missed that. Still no overly impressed to be honest but at least it is omega connected.
Hey ho.
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?
@Arshad-Alam
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.