PST.. develop a firmware change for the Pico SCPI labTool - unique USB enumeration ID

RE: PST.. develop a firmware change for the Pico SCPI labTool - unique USB enumeration ID

Jan Cumps — Sun, 27 Aug 2023 20:17:30 GMT

For the agile inclined, this is the current user story board.
Things we want to include in release 3 are assigned to the milestone "feature set 3". (our next release train)
Items that have previous been release are archived.

RE: PST.. develop a firmware change for the Pico SCPI labTool - unique USB enumeration ID

Jan Cumps — Sun, 27 Aug 2023 18:17:32 GMT

After testing this, I wanted to contibute my unique ID contribution to TinyUSB repository.
Only to find out that they have done the same 3 weeks ago [emoticon:c4563cd7d5574777a71c318021cbbcc8].

A bit different: they did not put any pico code in the example file.
They abstracted it out to a new function in their api: hw/bsp/board_api.
Then they implemented that function for all boards that they support. For the Pico in hw/bsp/rp2040/family.c.

Once Raspberry deploys a new SDK, I can unwind my code and use the new TinyUSB approach.

RE: PST.. develop a firmware change for the Pico SCPI labTool - unique USB enumeration ID

Jan Cumps — Sun, 27 Aug 2023 16:50:25 GMT

For the curious: this is what's been contributed to development, not yet released:

RE: PST.. develop a firmware change for the Pico SCPI labTool - unique USB enumeration ID

shabaz — Sun, 27 Aug 2023 15:29:01 GMT

Great blog post!! This is excellent to see the complete process to creating a very useful feature! The testing information is super-handy.

It will be great to see what ideas people come up with (and the good thing is, not everyone needs to be good at programming, some can suggest features, others can dip their feet gently into coding by making an incremental improvement if they wish).