We tested GPIO in the general version 36.2. Found a problem.
As a rule of thumb, and as described in the latest Developer Guide, you should perform operations under the /sys/class/gpio/ path.
We use custom carrier plates,
One thing is clear, the same board, using the L4T35.3.1 and L4T35.4.1 version did not appear this situation.
In fact, our problem is that in the L4T36.2 version of the system. The /sys/class/gpio directory cannot be found.
Please note that the software stack in R36.X is much different from R35.X and we suggest using GPIO character device API instead of sysfs to control GPIO.