Closed microenh closed 1 year ago
Thanks for looking into this! Do you think you can create a pull request for these changes, so that you get credited properly in the commit history?
You will need to fork the repo (so you get a copy of the repo in your account), and then edit + push your changes to your fork. Then, you will have the option to create a pull request here using the changes from your fork of the repo. More info: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request
There's also an 'edit' button on the files which you can see in the GitHub web interface, which will basically fork the repo for you and let you edit the files you want. See https://docs.github.com/en/repositories/working-with-files/managing-files/editing-files#editing-files-in-another-users-repository.
Thanks! Re: openocd, since picoprobe now supports CMSIS-DAP, we can just use the upstream version instead of the RPi fork. I have scripts which build that correctly, will add those after your patch.
Closing this issue as this is addressed in #30.
The installer is failing when building picoprobe and copying documentation from RaspberryPi.org.
The picoprobe failure is because the picoprobe repo has added submodules which are not cloned.
The documentation is failing because the RaspberryPi website has changed.
I have attached modified files that appear to correct these issues.
pico-docs.txt pico-setup.txt
I couldn't upload the files with the proper file extensions.
pico-docs.txt should be renamed pico-docs.ps1 pico-setup.txt should be renamed pico-setup.cmd
I was unable to build openocd while building the installer.