[ 20.900878] device eth0.1 entered promiscuous mode
[ 20.905758] device eth0 entered promiscuous mode
[ 20.940478] br-wlan: port 1(eth0.1) entered forwarding state
[ 20.946310] br-wlan: port 1(eth0.1) entered forwarding state
[ 22.939289] br-wlan: port 1(eth0.1) entered forwarding state
[ 24.809528] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: 8701d944
[ 24.823293] Rebooting in 3 seconds..
This Kernel panic is a known bug of the closed source MediaTek WiFi driver. Now we know it can not manage if there is a WiFi AP in the neighborhood with some Unicode character in its SSID.
Onion @administrators deeply kept silent about this bug.
It seems Onion's new WARP CORE driver (also closed source ???) can manage this situation.
Unfortunately Onion @administrators do not say too much about this bug feature (as usual ;-).
@György-Farkas kernel was corrupted for sure, that's something I can tell you with honesty. The device was literally dead, only after inserting a microSD card with a new firmware my device was able to update itself and become functional.
Well... no one but you should know if this correct (or not ;-)
my Omega2+ will "shut down". I can't access the Wifi AP and the LED is off.
If you find your board in the state you described again, before you do anything with it try probing the SPI lines with a logic analyzer. If you see activity it means that your Omega2+ suffered an unexpected reboot and the SoC primary bootloader is trying to load U-Boot using 3-byte addressing, but the SPI flash is still configured to use 4-byte addressing. (refer to Omega2 reboot for more info on this issue). If this is the case you have to power-cycle the board in order to get it to boot again (which resets the SPI flash addressing to 3-byte mode)
@György-Farkas it was about 2h 30min, most of time it was idle. I consider to put there QI receiver coil for wireless charge. Actually the lack of hibernation or sleep mode could be potential problem in future.
Thank you. At least now I know why it isn't working maybe some rainy sunday I'll try to look into the code and fix it I have some experience pulling json data like this for other projects on ATMEGE328p and ESP8266. The Omega is almost overwhelming me with all the features and coding options, but I like it.
I made the newsfeed work instead and will adapt that into to train time display for my husband.
The jist of it is that you'll need to use the Build System to do your cross compiling. If you need a separate library for your program, it will first have to be built by the build system before you can include it in your program.
My question is if i connect a switch only with 3,3V and an input GPIO, could i always read the correct input? That option is necessary to keep my cable management.
Maybe its to be realized by using analog inputs with the arduino dock.
@Douglas-Kryder , I looked though all of the openly available documentation. The only document which addresses low-level stuff like peripherals and general SoC behaviour seems to be the Datasheet.
@luz , I did find that MT7628_ProgrammingGuide, but in a first look it seemed to have pretty much the same content as the datasheet... But thanks for the info, I'll be looking for stuff on both documents now,
What you said about the different market positioning is true. As a product developer the main reason for going with MT7688 (and Omega) has to be the price, which seems to be unbeatable. Unfortunately we can't have everything...
you might find some clues by researching either the hologram dash or the hologram nova. the dash was in development about the time of the onion gps module and the nova is the newest gps module which is similar usb module. there are several guides on net explaining how to setup nova on rpi which might help setup onion gps on rpi.