add support for micropython on RP2040 boards #14
Conversation
|
p.s. i have not included the pre-compiled binaries in the PR yet in case they change during testing. as a reviewer you will need to generate them yourself. fortunately it is as easy as:
p.s.s. perhaps this script could make a good candidate for continuous integration |
w/o issues copying binary files we are able to use the main ```__init__.py``` file from the Qwiic_Py repo, thus deduplicating code all that is needed is to add the micropython_rp2040_i2c.py driver to the list of drivers, and also copy additional drivers to the target b/c they are imported within ```__init__.py``` updated instructions to point toward improved ```pico``` branch of rshell
also fix a few bugs with bytes/bytearray usage
|
latest pushes run on the rp2040, however there seems to be an issue with block reads that causes only zero to be read back. more information is needed at this time |
There was a problem hiding this comment.
Comments/Feedback:
README
- Start this with the general concept- this will install pre-compiled files onto your board
- List out the supported boards ( - full names and links to the boards on our site)
Getting started section - keep it high-level, easy to follow. Specifically
- Outline the use of rshell and the tweaks needed for it to work with the rp2040, and then just show the commands used to copy the files to the specific board. I'd include code sections fo each of our boards (SO someone can just copy and paste these commands).
- Add any commands need to copy examples over
- Show example running example using the RPEL
Below this, discuss details
- how to create the mpy files
- Contents and structure of the micropython folder ...etc
Basically, keep getting started at a high level, and make it the first section of the document. This is what most people will use.
MPY GENERATION
- Should this be a GitHub action?
micropython/tools/qwiic_mpy/gen.py
- rename to mpygen.py
- Add comments and description to code.
- Switch source to 4 space tabs, not 2
micropythong/tools/qwiic-mpy/push-driver
- The names of these should follow the template rp2040_.rshell
- All lower case
- Note: the PiMicro is now the promicro
micropythong/src/qwiic_i2c/init.py
- What does this exist??
- A better solution is to add exception handling around the loads of the other platform drivers in the driver logic of the main qwiic_i2c repo. Basically a try-except-else block. where the driver is loaded in try, execution is a pass, and else adds the driver class to the "_drivers" list.
I can provide further details if needed.
** Board Files **
- Update the names of the board folders to be rp2040_ and all lower case.
|
addressing comments:
re: github actions
note: at the moment i am unable to add demo output to the README - i am away from my test hw. i will get back to this as soon as i can however it should be possible for others to modify this PR so anyone else may add it if they have demo output handy |
|
Jumping in here with a question, as I’m working with MicroPython on ESP32. The board I have here has a Qwiic connector, would this PR be a starting point for having that supported in MP? / any progress on having this merged in general? |
what it do
micropython/tools/qwiic-mpy/gen.pywhich can be used to generate and update bytecode (.mpy) files for micropython from the Qwiic_Py sources..gitignoreso that.mpyfiles are ignored except within themicropython/distdirectory, so that users can access pre-compiled filesmicropython/README.mdwhich explains the basics of how to use everythingdependencies
add micropython RP2040 i2c driver - this is necessary b/c it contains the i2c driver for micropython/rp2040
status
⚠️ additional boards can be added (non-blocking)
✅ build script
✅ module compatibility with filesystem
✅ i2c driver seems to work
✅ device driver testing satisfactory