Glad to hear it!
While the buildroot is nice, nothing quite like having 10’s of thousands of packages ready to install with a mainstream distribution!
honestly i absolutely love embedded linux, just don’t have the time to play with it, i could keep myself busy for weeks or months making my perfect thinggy. but falling short of that, alpine is awesome. (tbh the alpine devs just did that exact thing 
Just a note on the use of WiringX. While it is fine, it ultimately makes calls to ioctl(). Which you can easily implement for just about any of the I2C, SPI, or other protocol you need. I’ve found it much easier to simply use the kernel facilities (e.g. i2c-smbus or spidev) over ioctl() than to hack WiringX.
Totally up to you, just know there is another option if WiringX gives you too much grief.
@drankinatty thanks for the advice, will help many I think. I got thrown off by the non-working demo project - only wanted to know if the second core was even active. I hope later to understand and be able to use it as you say. (Gonna try to get a little robot arm that’s controlled by it, but its more like a 2025 project. Just saw the braccio robot is like ~$300, at that price I could even grab the smallest KUKA arm out of some insolvency lol)
Hi, there. I tried using USB device via IO-Board through that the alpine image. but it didn’t work(no such log in dmesg and lsusb). Is it problem of my Duo? or image defect?
Hi, I think I successfully used an USB device. BUT you need to first turn off the rNDIS USB over ethernet (where the docs tell you to remove the script or you can also remove it from the rc-update service list).
Otherwise the USB ports were dead.
I don’t know why it’s like that / why there’s such a hard interdependency. but it should help with this problem.