I was looking for a release image for the RP Pico 2. I see the release for the RP Pico (i.e AtomVM-pico-v0.6.6.uf2) but was expecting to also see AtomVM-pico2-v0.6.6.uf2
If needs be I can build my own image but figured I’d ask before going down that path.
tia
Support for Pico 2 in is in the main branch, but was not backported to the release-0.6 branch. Release binaries will be available for Pico 2 devices starting with release 0.7. In the meantime you will need to build binaries for Pico 2 from the main branch.
I recommend following the Build Instructions, note this also requires doing a generic_unix build, this is step builds the BEAM libraries (atomvmlib.uf2).
We don’t have a timeline yet on when to expect 0.7 to be released. The main branch may already have some breaking changes from 0.6.x, and more are to be expected before it is released. Make sure you are looking at documentation for main when working with this branch, and if you spot any errors or undocumented changes please open an issue so we can get them corrected before we do release AtomVM 0.7.
Happy hacking,
Winford
Fab, thank you. Now I know I am not overlooking something obvious I have gone ahead and built from the main branch.
Can you share the build somrwhere?
Or at least the instructions.
That would be much appreciated!
Ok, managed to build them.
Feel free to download. Though it’s not tested yet.
It sounds like you already figured it out, but just in case you missed something here is a link to the pico build instructions:
Do note that the libraries are built as part of the generic_unix build, so for a complete deployment you will need to build for generic_unix and rp2 platforms. This may change at some point in the future, we are reorganizing libraries and discussing a different approach for libraries (possibly releasing them on hex.pm, to be pulled as needed for application dependencies).
Let us know how it goes, and don’t hesitate to open an issue on GitHub if you run into problems, or find anything lacking, or inaccurate, in the documentation.
I’ve been looking at the California law that comes into effect next January
about age verification. It isn’t clear to me that micro-Python and AtomVM
aren’t operating systems (considering that the RPi Picos don’t have any
other OS under them and they can load and run code) and that flashing them
onto the chip isn’t setting the “OS” up. I haven’t read the corresponding
Brazilian law that comes into effect next week, or the Colorado or New York
drafts. The California “Age Verification” law is worrisome enough by itself.
Has anyone obtained legal opinion about whether AtomVM (or any other
programming language running NOS on embedded chips) is affected?
[Let’s not go into whether a law that explicitly disavows having anything
to do with the person using a device will do anything to protect children
whose devices are “set up” by their parents or school technicians. This is
just about whether AtomVM can be legally distributed in Brazil from next week
or in California from next year.]