There may not be a mpu6050 module? If you can talk to the i2c bus directly, you could talk to it straight from the user mode.
If i2cdetect doesn’t find it, then one of the following is true:
- the MPU6050 is broken
- the MPU6050 is not getting powered
- the MPU6050 uses different voltage than the Jetson (3.3v vs 1.8v can be a problem, depending on options/jumpers)
- the MPU6050 runs at a slower i2c max clock than you’re using on the Jetson
- the MPU6050 is not connected with correct pull-ups
- you’re talking to the wrong i2c bus on the Jetson and the MPU6050 is connected to another bus
- the GPIO pins are not configured to output the I2C signals
Depending on which of those are the problem, you will need to do different things to fix them.
I’d recommend hooking up a logic analyzer to the I2C bus and ground when doing the i2cdetect, to make sure you actually see the clock/data wiggle correctly.
Once you can make sure that happens, you can start debugging the actual communications protocol.
A good logic analyzer for hobby and semi-pro work is the Saleae Logic series. I started with their cheapest option (when it was $89) and have kept upgrading until I now have the Logic Pro 16. For a beginner, the $109 Logic 4 is probably sufficient – it lets you debug one SPI or two I2C or two UART at the same time.
The reason I like the Logic is that the software Just Works, and is very easy to use, and the devices are robust. There are cheaper options from China, and more complex options from various technical vendors, but I’ve found them to be harder to use and less robust.