My board is not booting after attempting to enable the i2c following this guide:
Following the instruction, I misread one and input:
sudo usermod -a -G i2c [My User Name]
sudo usermod -a -G i2c $USER
upon reboot I get a null MAC address, DT failed -99, and i2c failure.
after power off and on again, the device now just sits at the NVidia logo.
I believe what I’ve done is overwritten the i2c address, I’m hoping this can be fixed via serial comms, which I’ve ordered a cable for and am waiting on it being delivered.
But I could use help in knowing if this is what I’ve broken, and if it is fixable?
And what steps I should take to fix this, or further diagnose it.
Hi, I got one of the devices working completely, and another 2 that looked like they were working completely, but they will not recognise an ethernet cable when it plugs into them (but use wifi fine).
The i2cdump -y 0 0x50 for the working board is:
The main difference I can see is in line 01, where it doesn’t seem to pick the same EEPROM version, as well as different module ID’s, and “NVidia reserved” memory.
Worth noting is that the non-functioning device is on a completely fresh flashing of ubuntu 5.2.
image 1 is the working board, image 2’s board is not detecting anything in it’s ethernet port. (or not detecting the ethernet port as existing at all).
I’m assuming this is related to the prior issue as it’s the only thing that has been done to this board.
Sorry for the late reply, I hadn’t noticed this issue until today when working with the board.
The intent is to have this board on-site and using a LAN network via a router to control devices on the network, so the missing ethernet connection was what brought my attention to this issue.