Also, can you try latest GPIO Tool v1.2, I tested on same application version.
Yes, same issue.
I have done some more investigation. The issue seems to happen when I setup some pins in the config block GPIO. However, the pins I’m setting up in the config block isn’t the pin I’m having trouble with in the GPIO utility.
I have setup pin 146/GPIO 111 and pin 100/GPIO 92 in the config block as ouput high, like this:
- set gpio.XX.ctrl=1
- set gpio.XX.obe=1
- set gpio.XX.dse=1
- set gpio.XX.state=1
Cold boot, launch Vybrid GPIO Utility v1.2, change pin 28 from low to high, the GPIO Utility still shows pin as low but the pin is high (verified with beeper sound on custom base board, and verified with volt meter on Eval board).
If I zero out the config block GPIO, it works fine.
Not sure why, but setting pins 146 and 100 in config block GPIO prevents the GPIO Utility from showing the correct level when I change pin 28.
So in summary, there is still a bug in the GPIO Utility that doesn’t properly show the gpio level if other pins have been configured in the config block.
If you have Toradex Colibri Evaluation
Board, try to do the same test on it,
remove JUMPERS and test it using
multimeter and GPIO tool.
I tried this. I put the module in the Eval board, removed jumper labelled sodimm 28 and connected a volt meter. Cold boot, launch GPIO Utility, change pin 28 to high, and the volt meter goes from 0v to ~3.2v, but GPIO Utility still shows “0”.
Only one thing I noticed, if you have
ColdBoot (RESET) your device then by
default SODIMM 28 should be configured
to GPIO INPUT LOW, but in your video
@00:20 it is showing GPIO OUTPUT LOW,
this do not seem to be correct.
Pin 28 by default is GPIO output, not input, at least that is what I am seeing. I have not configured pin 28 in the config block, so that is what its defaulting to for me. Is that a problem?