i'd suggest a power supply of 5V 2A minimum. usb lines from computers and/or phone chargers most of the time do not supply the current that the omega2 needs to boot up. especially at the point where the omega2 attempts to connect to a wifi router and can generally require for a brief period of time current in excess of what a usual usb line or phone charger can provide.
you will need to get a copy of the *.bin from the onion server somehow which requires internet. you can try to download directly from server.
http://repo.onion.io/omega2/images/ and then flash that.
look in the documentation for the instructions.
https://docs.onion.io/omega2-docs/
look for download to usb storage.
https://docs.onion.io/omega2-docs/manual-firmware-installation.html
if you have a dock with usb then,
https://docs.onion.io/omega2-docs/usb-storage.html#usb-storage
otherwise a serial cable will help in the transfer.
try a space between ) and { on first line
int main() {
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.
there might be some info in these documents that would help,
https://docs.onion.io/omega2-docs/using-ethernet-expansion.html#using-ethernet-expansion
https://docs.onion.io/omega2-docs/omega-router.html#omega-router
https://docs.onion.io/omega2-docs/ethernet-bridge.html#ethernet-bridge
@Caio-Mehlem said in Documentation for MT7688:
Programmer’s Guide.
take a look at this page,
https://docs.labs.mediatek.com/resource/linkit-smart-7688/en/documentation
maybe create a method to data log the power [volt/amp] supplied to the omega2. you would then have a record of what was being supplied immediately prior to shutdown. maybe heat build up over a day or so affect the output of the power supply. maybe the script you are running affects the load on the omega2. i suspect that 200mA max of supply [if it is that] might be not enough under some conditions. maybe what ever you are using to supply power to the board is turning off/sleeping at some point because the omega2 is not using enough current.
@leonardo-moura you may find a way to use the onion arduino dock2 [sold separately] to handle the screen and then report to that screen whatever it is the omega2 is doing but the screen alone with omega2 most likely no.
@CAP-33 i have been issuing a reboot from a ssh terminal and then watch the device and when the LED goes off i remove power. so far i have not had an issue with data loss. i do remember when the device was first released the suggestion from an onion rep was just unplug it at any time.
@György-Farkas the out of the box state is continuous illumination. that is the manufactured normal state. any other state needs to be arrived at by user software control. that is a user defined state. look, you can beat this to death if you want, but i'm looking for help which you seemingly do not want to offer or can not offer. so why the trolling? please, just leave it effing alone.
@György-Farkas thing is i realize it is possible to blink the LED if one wants to do that. however the normal state of that blue LED is to be continuously illuminated and on my dock that is no longer the case. hence this request to anyone that might have an idea about how to restore the continuous illumination. it seems it is a hardware component failure or near failure that is happening and so if anyone has any insight into what component it might be i'd appreciate knowing. thanks.
watch this video if you need to see the normal LED state,
https://youtu.be/fo_KEEIQO9M?t=285
@György-Farkas hi, that is not my understanding of the dock LED. this particular blue LED did stay illuminated during operation. although the following clip is short you can see that the blue LED is continuously illuminated. the blinking LED of the arduino is done via an external LED.
https://www.youtube.com/watch?v=u5o5xAGO6ck
https://docs.onion.io/omega2-arduino-dock-starter-kit/arduino-kit-blinking-led.html
the power LED on my ardunio dock 2 has, after 2 months of being powered continuously, ceased to stay on. however it does flicker at times and at other times remains very dimly illuminated. the dock itself appears to be working ok. i was able to install the arduino dock 2 software via opkg again and i can still do wireless transfer of sketches and they run ok. but still i'm left wondering if this is a problem. the LED itself still functions as it will at times burn normal brightness for short periods. i'm just puzzled about what the issue could be and if there is a possible fix either hardware or software. if anyone has an idea about this i'd appreciate some feedback. thanks.
@ice-long you might want to think about doing the procedure described in the documentation.
https://docs.onion.io/omega2-docs/boot-from-external-storage.html
@Christopher-Bunnell the dash is probably pretty similar to the onion hologram since they were pretty much developed at the same time. if you can find the pinout sheet for the dash and also the pinout and maybe tech reference for the onion you might be able to cross reference the pins that onion uses with the onion cellular and just match those same pins from the dash and using wires plug those dash pins into a onion expansion, anyone of the expansions should do.
@Maximilian-Gerhardt you sorta out did even yourself with this post :)
thank you. it will be very helpful.
@Simon-Cain hello, just wanted to add that the mac address on my omega2+ also changed.
the link just re-directs to this page. you have any more cool tricks?
worth mentioning that the 5 "accessible" ethernet are on the omega2s which is quite a bit more expensive.
i've tried the oupgrade twice and neither one worked. it goes through the download and certainly looks like it is working but then omega2+ just blinks for 40 min each time, btw running very hot, and then i just reboot and when it comes back up it shows a new b160 installed. i guess i'm gonna try a sysupgrade later.
edit: i tried a different omega2+ and the oupgrade routine worked well as did the overall installation.