Quite fresh report of some SPI related issues, not investigated, neither proved it has anything to do with E9:Does it affect ANY GPIO, e.g. also used via peripheral devices, such as SPI (via ALT, not using PIO or GPIO bit-banging)?
https://github.com/raspberrypi/pico-feedback/issues/409
It has nothing to do with the pin erratum.
(1) Now that the updated datasheet and E9 description is out, could you please elaborate a bit? (I wrote pico-feedback #409 by the way - note the EDIT at the end if you've missed it perhaps.)
(2) If you can conclusively and absolutely dismiss this as not E9 related, should we read into this statement of yours that you're instead aware of some other issue - possibly lingering SDK 2.0.0 gremlins? - affecting SPI, as experienced by me and seemingly others in this thread?
(3) Is there any official ETA yet on when a fixed "A3" silicon might be on the market?
(PS. For the record, my Pico-carrying product interfaces with 2 devices on SPI0, 4 devices on SPI1, and up to 10 devices on I2C, while also utilizing all remaining GPIOs for other purposes, and I've only seen these occasional glitches - then affecting all SPI1 devices by the way; not absolutely sure whether SPI0 was affected too but I believe so - since migrating my development rig to RP2350A0A2. Unfortunately, as I also noted in #409, it's hard to trace something that comes and goes, regardless of whether the underlying issue turns out to be HW and/or SDK/SW related. Of course, if/when it rears its ugly head again, I'll try to dig deeper...
)Thanks!
Statistics: Posted by xoblite — Fri Sep 06, 2024 11:07 pm