Seth:
I don't think the software commands can see any closer to the pins than the
I/O registers associated with the pins.
Physical or electrical damage to the pins, such as damaging the ESD diodes,
or damaging an I/O transistor might not change the behavior at the I/O
registers.
If you want to t
Hello Graham,
Seth here. Okay, I will just check to see if they are working. I thought
the distro could detect our hardware and if it was in working order or not.
I know of the *i2cdetect *command to see if the hardware is available but I
thought there was a software to detect if the hardware s
I don't know how to do a pure software solution.
If you want coverage of the BBB Hardware all the way to the pin, I would do
a simple loop-back test, where the pins are connected in pairs, and you
wiggle one pin as an output, and see if its paired pin can see it as an
input.
Then reverse and wig
Hello,
I am still looking around for test options for the Debian OS on our BBB. Do
you know how to test the P9 and P8 headers on our boards with software?
Seth
On Thursday, July 27, 2017 at 7:28:09 PM UTC-5, Mala Dies wrote:
>
> Hello,
>
> The other day is when I did some incorrect measurements
Hello,
The other day is when I did some incorrect measurements and almost burned
down the "world." Anyway, I need some support. What are some surefire ways
I can test my GPIO pins in the Debian distro with our commands?
Seth
P.S. I do not want to test them via hardware. I thought there might b
