9names

Immediately after jannic posted that link to the pico-sdk issue the raspberry pi folks posted this reply and then closed the issue: > We won't be providing a software workaround...

Not that I'm aware of. I've always written out the change myself, since not everyone clearly specifies the change in the PR name, and if they do they do not...

Interesting. Well, considering that winksaville can't create a release here, I went and did it. Here's what it spat out ``` ## What's Changed * Run picotool step in github...

Closing this PR as release 0.3.0 happened via #901

@therealprof what would you recommend instead?

how about 4 tests? ```rust instr_test!(r#in(InSource::Y, 10), 0b010_00000_010_01010); instr_test!(r#in(InSource::Y, 32), 0b010_00000_010_00000); instr_test!(out(OutDestination::Y, 10), 0b011_00000_010_01010); instr_test!(out(OutDestination::Y, 32), 0b011_00000_010_00000); #[test] #[should_panic] fn test_invalid_in_bit_width_should_panic() { let mut a = Assembler::::new(); a.r#in(InSource::Y, 33); a.assemble_program();...

@moritztim you need to remove the thing you said you would remove, exactly 1 post above ithinuel's reply: > I think the LICENSE file might not be needed. which is...

This is an incorrect read of the history of this template. The original intended method for using this template was cloning the repo or downloading it using the github download...

I just tested https://github.com/FlareFlo/magneto_pad rev 40235373fcf07a698b5d8caabe2ba2d4335adc10 with my pico (I picked a random commit from after this issue creation date and before it switched to stm32) and a nanoDAP-hs probe...

Actually: after reading probe-rs matrix, your issue is different. This one is specifically "can't ever communicate with the target", yours is a spurious error message. @rursprung please make a new...