Connecting OpenCR to Raspberry Pi 4 results in immediate corruption (EXT4-fs error)

[abinayadinesh1]

Hi!

I bought the turtlebot3 burger kit a couple months ago with the raspberry pi 4b, and have followed all the instructions in Quick Start Guide (https://emanual.robotis.com/docs/en/platform/turtlebot3/quick-start/#pc-setup) using ROS Humble and Ubuntu 22.04. I get immediately stuck when I start step 1 of the OpenCR setup where I connect it to the Raspberry Pi using the micro usb given.

While the OpenCR is still conntected, I start getting errors on my raspberry pi that says 'ext4-fs error: comm bash reading directory lblock3' and then '/user/bin/ls input/output error' when i type "ls"

i have reproduced this multiple times, have tried redoing the whole process cleanly with new a new image on the raspberry pi and even tried different hard disks and drives to see if that was the problem. i consistently get stuck every time I connect the OpenCR board to raspberry pi.

BTW, this is all being powered by a 28V usbc cable connected to an outlet that goes directly to the raspberry pi. The raspberry pi works completely fine with this connection, and the OpenCR board also gets indirectly connected through this power source.

Unplugging the openCR board and then restarting the RPI on the same image resolves the error, but now I still cant set up the motors.

Has anyone seen this before? Does anyone know if it is a problem with an OpenCR board or how i can start debugging?

[abinayadinesh1]

I think this is fixed:

1. disconnect raspberry pi and opencr from power
2. connect opencr to raspberry pi
3. connect raspberry pi to power
   the issue was i tried connecting while the rpi was still running.