@Adrian-Aguirre You may modify also the '/etc/opkg/customfeeds.conf' file and can use also OpenWrt 'snapshots' of course.
Q: I am a standard consumer, do I want a development snapshot firmware?
So - I think - it's much more simple to use the usual method.
Question about LiPo batteries and charging.
I'm going to take the battery to a friends house tomorrow that has a charger for rc cars and test it if anyone has any suggestions on troubleshooting.
@Bryan-French , after update new firmaware, of course i did need to create again, extended RAM, SWAP, and extra space (overlay), but i did use the old commands..
Just to verify you are able to reboot after these steps and see a larger overlay with df -h?
What is the command you are using to try and set up you swap file?
Ok since my device was available in the /dev/ folder as spidev1.0...given I assigned bus0 and deviceid 1 when I ran insmod...I was able to use the standard spidev library in Python to access this newly created spi device. The CS now goes low when I run my python script but I don't see any data or clock signals...I'll check for a conflict with the pins that I assigned to MISO, MOSI and SCK.
Will report back soon, if this works...then it's actually easy to implement software SPI.
I had an overlay setup with the older firmware that didn't work once I updated the firmware to the latest. I went to re-establish the overlay per the instructions on the onion site, but there is no /tmp/mounts folder any more. It appears as though there is an overlay setup already but would need to changed to the sd card? Are there updated instructions?
IIRC, the standard RTC package implements an init script which will read the data from the RTC device on boot and set the clock accordingly.
On shutdown it updates the RTC device with the current clock value.
In between those states, if a network connection is established, the Omega will query NTP servers and sync the clock with that.
So, as long as you build your firmware with the requisite packages (the one with the driver for your RTC device and the standard RTC package together with any dependencies either require) and ensure that the RTC device is accessible during boot up, your needs should be accommodated.
Updated to 0.3.2 b218 two hours ago (Omega 2+). Problem remains. Additionally static ip network setup fails now. Worked with the delivery version.
I'm using firmware 0.3.2 b217 (Omega2+).
Did as you suggested and MPC installed without problem.
I have no problem loading and playing a radio stream.
Oh one thing I forgot to mention, after I got all this working I was able to tar the node_modules directory up and move it to an Omega2S+ with no SD card.
After updating it to OpenWRT18, the nodejs install is small enough no external boot is necessary and there is no need for NPM on the production boards since they will never install a package. So that is nice to be able to eliminate the SD card.