I tried to use the jetson-io package to configure the 40pin header but immediately encounter error as shown in screenshot below. jetson-io complains about touch_clk_pcc4. I think it’s related to changes made to enable the SPE gpio app.
Is there way to get this working and use jetson-io with the SPE configuration changes?
I’m not sure about your operations.
If you want to operate GPIO from SPE firmware, please follow instructions in GPIO doc of SPE package. In that case, CCPLEX (Linux) cannot access those pins anymore.
Generally, the module can only be controlled by one entity, either SPE R5, or CCPLEX.
I’m not trying to use the same pin for both SPE and Linux. I’ve done the changes to use a pin from SPE and now want to use some another pin from Linux side for something unrelated. However looks like the SPE change somehow broke the jetson-io tool?
Hello, teemu1: After applying these the SPE GPIO example app works but the jetson-io does not.
That’s expected. It’s better not control one GPIO pin in both SPE R5 and CCPLEX.
Once it’s used by SPE firmware, please do not touch in Linux side, to prevent confliction.
Correct, I understand that. But the problem I’m trying to convey here is that after the SPE change the jetson-io tool fails immediately off the bat (when I select the menu option 40pin header). I’ve not even yet tried to do any configuration at this point.
Steps to reproduce.
Apply changes stated in SPE GPIO example app.
Start jetson-io tool
Select option ‘Configure Jetson 40pin header’.
I get the error on the screenshot
What I expected.
I can configure available GPIO pins (expect the ones reserved for SPE, those are pins 15 and 27 on the 40pin header).
Once you make changes as GPIO doc in SPE package mentions, the control is transferred to SPE side. That means all operations/configurations for desired pins should come from SPE side.
So you cannot run tools like jetson-io, in Linux side (CCPLEX) to control the same pin any more.
I’m not convinced we’re talking about the same thing now.
Just to confirm: Is it possible to control a different pin? Or does this mean that using a single pin from SPE side will make it impossible to configure anything else with jetson-io? Because where I stand it looks like this is the case.