home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   RBERRYPI      Support for the Raspberry Pi device      21,939 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 19,748 of 21,939   
   Michael Schwingen to The Natural Philosopher   
   Re: Need help with PI PICO...   
   24 Mar 24 13:31:48   
   
   INTL 3:770/1 3:770/3   
   REPLYADDR news-1513678000@discworld.dascon.de   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  e2681272   
   REPLY:  5ebf554b   
   PID: SoupGate-Win32 v1.05   
   On 2024-03-23, The Natural Philosopher  wrote:   
   > My choice tree  is between the GPIO out signal never being received by   
   > the ultrasonic module, or the GPIO in signal is being missed by the Pi   
   > PICO on account of possibly some interrupt masking its appearance until   
   > it is too late and its gone low again.   
      
   Or there never is a signal on the module output.  You should write your code   
   to cope with such problems - sample code/libraries often skips the error   
   handling, but that does not mean *you* can if you want reliable operation.   
      
   Hook up an oscilloscope or logic analyzer to check what is the case.  A   
   cheap 8-channel USB logic analyzer is a great tool to have around when   
   working bare metal:   
      
   https://www.aliexpress.com/item/1005005993277484.html   
      
   Using the Saleae software on these is *not* allowed by the license, but   
   sigrok/pulseview work great:   
      
   https://sigrok.org/   
      
   > We are running bare metal-ish here.   
   > Back in the day I would have used a chip emulator with hardware break   
   > points.   
   > And a cost of hundreds of thousands.   
      
   Nowadays, you would use a SWD debugger, since the debug/emulation logic is   
   already integrated in the RP2040!   
      
   Something like the JTAG Hat on a Raspberry PI:   
      
   https://www.schwingen.org/jtag-hat/   
      
   or any SWD probe supported by OpenOCD (FTDI, CMSIS-DAP work fine), like the   
   Raspberry Pi Debug Probe (which works for the RP2040, but lacks reset   
   signals and support for voltages other than 3.3V):   
      
   https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html   
      
   That sets you back about 20€, and gives you instant breakpoint/single step   
   operation with full view of registers and memory contents.   
      
   cu   
   Michael   
   --   
   Some people have no respect of age unless it is bottled.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225   
   SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 111 112 113 200 206 307 317 400   
   SEEN-BY: 229/426 428 470 550 616 664 700 240/1120 266/512 267/800   
   SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757   
   SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1   
   SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5058/104   
   SEEN-BY: 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca