linguini1 opened a new issue, #13483:
URL: https://github.com/apache/nuttx/issues/13483

   ### Description / Steps to reproduce the issue
   
   There has recently been an update to support building the Raspberry Pi Pico 
NuttX image using the newer 2.0.0 version of the Pico SDK which you can find 
here: 3f00c4aae08fc4b564d4b017fa2896f6e98a315f
   
   The [documentation on the NuttX 
website](https://nuttx.apache.org/docs/latest/platforms/arm/rp2040/boards/raspberrypi-pico/index.html)
 suggests using version 1.1.2, which no longer works as part of the build 
process. I suggest updating the instructions in the documentation to use the 
2.0.0 version of the SDK and direct users to the picotool GitHub repository 
where installation instructions are present.
   
   **Steps to reproduce:**
   Follow the instructions in the linked documentation step by step on the 
latest version of NuttX.
   
   I have also tried going back before the commit adding support for 2.0.0 (so 
pinning to commit 1b245664ad665679fbee494994e0cf3ed0acea4b) to attempt building 
with 1.1.2 the old way, which no longer works either. It appears 
the`boot_stage2` directory that the NuttX build system expects under 
`src/rp2_common` is actually in `src/rp2040`. It seems like changes in the 
directory structure in the SDK were back-ported to older versions, but I can't 
find any evidence of this in the commit history of the SDK. It does seem that 
older versions of NuttX will not be able to build the Pico image the same as 
the old docs state because of this.
   
   ### On which OS does this issue occur?
   
   [Linux]
   
   ### What is the version of your OS?
   
   Arch Linux 6.10.10-arch1-1
   
   ### NuttX Version
   
   master
   
   ### Issue Architecture
   
   [arm]
   
   ### Issue Area
   
   [Board support], [Build System]
   
   ### Verification
   
   - [X] I have verified before submitting the report.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to