search

v923z / micropython-builder

Ready-to-run firmware files with micropython and ulab
MIT License
26 stars 11 forks source link

Firmware for Pimoroni Pico W and ulab #23

Open ipiriyan2002 opened 9 months ago

ipiriyan2002 commented 9 months ago

Hey, I am new to this type of work and was wondering if there is a framework for Pimoroni Pico W and lab. I need it for my project and am unsure as to how to do it since I am unfamiliar with C.

Thank you

v923z commented 9 months ago

I think what you have to do is check, whether your MCU is mentioned herehttps://github.com/pimoroni/pimoroni-pico/blob/main/setting-up-micropython.md. If so, then you look at the workflow files in https://github.com/pimoroni/pimoroni-pico/tree/main/.github/workflows, and see what's under the section corresponding to your MCU.

ipiriyan2002 commented 9 months ago

Thank you. I actually got it to work afterwards with pretty much the exact steps you mentioned.

v923z commented 9 months ago

Do you want to contribute your scrip here, so that it would be built automatically?

ipiriyan2002 commented 9 months ago

The method I followed included forking the pimoroni pico repo and then adjusting the picow cmake file to include ulab and remove some sensors I did not need. So I am not sure I can really contribute a script per say since it was more of less using the workflow they had in place to generate the uf2 file and since its more specific for my use case.

v923z commented 9 months ago

That is pretty much what would be required here. If you look at the scripts in this repository, they're really simple, most of them just two lines of bash.

ipiriyan2002 commented 9 months ago

ok, I will give it a try. Kind of new to bash and c programming so bear with me!!

ipiriyan2002 commented 9 months ago
image

So I am wondering how I would create the bash file if I had manually changed the pico cmake file they already had in a forked repo's custom branch. Something like above. How would I tell the system to look at my forked repo's custom branch?

Again, apologies, I am not the most proficient with C or GitHub actions

v923z commented 9 months ago

I think we would drop the script here https://github.com/v923z/micropython-builder/tree/master/scripts/rp2, and then add one more entry here: https://github.com/v923z/micropython-builder/blob/master/.github/workflows/build.yml. If you don't want to deal with this, you can just post your makefile and the make command you used, and I would be happy to add that to the workflow file.