Was really in a crunch on this one and needed to get it working, so I ditched OnionOS all together in favor of vanilla OpenWRT 18.06.5
I followed the first two steps here https://yoursunny.com/t/2019/omega2pro-openwrt/
I removed the -F from the command as it is not needed in my situation. I then had to locate and specify the correct file path.
Within minutes, OpenWRT was running flawlessly on the Omega2+
I connected to my home network Wifi AP and disabled the Omega2+'s access point by selecting "replace current wireless etc etc"
I then followed instructions here https://www.circuidipity.com/openwrt-bridged-repeater/ for bridging the wifi through ethernet which worked flawlessly upon the reboot.
I now have the BeagleBone Black (powered via 5v adapter) connected to a USB hub, which powers the Omega2+ as well as connects the Beaglebone to the webcam and 3D printer.
Test print is running now to see if the timelapse renders, which was the issue with running Octoprint on the Omega2+ directly; the timelapse would be captured and visible in unrendered timelapses but would crash the Octoprint server at any attempt to render.
The other motivation for switching was to get away from the baud rate limit on the Omega2+ which required me to run custom firmware on my TAZ6 as default firmware all runs 250k baudrate due to performance issues with 115.2k.
Hopefully this helps someone else in a similar scenario.
tl;dr for Onion developers: Your documentation is inaccurate and/or out of date. Had I been able to use the Onion Omega2+ as a Wifi to Ethernet bridge as described by your documentation I would not have had to ditch OnionOS/firmware entirely.
Please update your documentation so that a person could, if desired, use the Onion Omega2+ as described, out of box.
After working around the shortcomings of the device & documentation, I am pleased with the performance of the hardware using plain OpenWRT 18.06.5
Thanks @luz you give me a lot to think about. I am using Omega2S+ and my custom board doesn't have an ethernet port. Due to my form factor I don't want to add an ethernet connection but I was considering adding a non-standard plug and make some custom tails so i can plug a temporary RJ45. Thanks for the tip on the ipv6.
@Modest-Polykarpovich not my own, but I'm still trying to improve existin driver, here my post, I add some of my fixes, It works better with them, but not perfect with rates higher than 96kHz, I really wanna play bit-perfect 192/24 on i2s Omega2
Another scenario is if I boot the Omega2 up with the battery attached and using USB power and then disconnect the USB power, the Omega2 continues to operate. But... if I re-attach USB power again, the Omega2 dies (and the orange LED goes off and the AP stops to work). Power LED is still on and if I have anything presented on the attached OLED expansion, it still shows even if the Omega2 is not working so the hardware stack has power coming into it.
Fairly common problem I've seen. What I do to overcome it is use a really good power supply (>=2A) and a short USB cable with thick gauge cable.
Typically I see it when powering the device via USB with battery attached and then there's a power failure. The device continues to run on battery, but as soon as the power returns, it dies. Solution = short, thick gauge USB power cable.
tried 115200 8n1 to serial console on usbc port . it is detected as a cp2104 usb to uart bridge with serial app i use to program network switches .
video of unit with flashing lte and faintly flashing power led . no other lights . tried several cables and plugging into macbook . also tried usb power adapter . it is drawing some power , but no wifi or console output . video of board
All fine. I was able to solve this problem this way:
./feeds install libffi
./feeds install libffi-devel
./feeds install python3-dev
cd .. and run make -j
(build failed again)
copy libffi* to /usr/lib
enter to source folder and run make -j
All together, looks like the build system doesn't look in the right place for libs but instead in host /libs folder.
Just writing if someone runs into same problem to know how to solve.
@Robert-Meagher, I had the same problem. The problem is in different version of OpenWRT repository, that now version 19 and older version Onion OS that based of version 18. MyPrepaidBalance
Your opkg manager is downloading packages from OpenWRT 19, that using GCC 7 or higher.
I fixed it by installing GCC with flags: force and without dependence, than all the dependence was installed manual. The list of depends you can found in the OpenWRT repository.
Now I'm using GCC 7 on the Onion OS (based OpenWRT 18), with no problems includes GDB debugger.
There seems to be a conflict between the standard Omega opkg sources and the lede-based sources that the Onion guys said to add to distfeeds.conf. lede sources want to install a later version of gcc and gdb, and dependencies get out of whack.
I don't recommend to use "live-compile", because you will have next problems:
Difficult use third-party libraries, because IPK (OPKG's) packages installs without lib_____-dev sub-package. In that case you need to manual copy it from cross-compilation toolchain.
Target-machine (Onion) also hasn't got some of system-only headers (.h-files). May be it never needs for you, but if another one case it will be problem.
Compilation takes a long time even simple projects.
In any case you have to install cross-compile toolchain, but I recommend install GDB on target (Onion) machine, because remote debugging doesn't works. Version of gdbserver and gdb (linux's or windows' hosts are don't work)
Now I'm writing big manual with a C-templates to fast install and deploy SDK and make native applications.
That helped. Thanks!
Looking at detailed implementation of mtd, I see that it'll be a hard task to make W25N01GV work:( The official linux kernel support for that NAND started with version 5.0.... So it looks like I'll end up writing a C-code to handle the chip only from my application.
Looks like your connection to Community was lost, please wait while we try to reconnect.