# Error when converting a mender Debian image

**URL:** <https://hub.mender.io/t/error-when-converting-a-mender-debian-image/7672>\
**Category:** General Discussions\
**Created:** [March 27, 2025, 4:47pm UTC](https://hub.mender.io/t/error-when-converting-a-mender-debian-image/7672 "2025-03-27T16:47:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adhn](https://avatars.discourse-cdn.com/v4/letter/a/919ad9/32.png) [@adhn](https://hub.mender.io/u/adhn)\
**Post date:** [March 27, 2025, 4:47pm UTC](https://hub.mender.io/t/error-when-converting-a-mender-debian-image/7672/1 "2025-03-27T16:47:14Z")

</div>

Hi!  
I have a Raspberry PI, and a clock module attached on its pins and an Arduino connected to it via USB.

[Here](https://hub.mender.io/t/error-when-generating-artifact-for-system-update/7528), I have mentioned that the mender Debian image was successfully created.

Now, instead of an Arduino, I use an ESP32 module, which is attached to the clock’s TX/RX input. In order to be able to communicate with the ESP32, I made the following changes:

```auto
in /boot/config.txt:
dtoverlay=uart0

in /etc/udev/rules.d/99-com.rules:
add ", MODE="0666" to the block "KERNEL==ttyAMA0..."

Execute the following two commands:
sudo udevadm control --reload-rules
sudo udevadm trigger

Remove the following in /boot/cmdline.txt:
"console=serial0,115200"

Configure the serial port:
stty -F /dev/serial0 9600 raw -echo

```

I did all the exact same steps to create a mender debian image.  
However, with Arduino it works, but with ESP (and using the above configuration) it does not.  
How do I fix this?

Thanks

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [April 2, 2025, 11:36am UTC](https://hub.mender.io/t/error-when-converting-a-mender-debian-image/7672/2 "2025-04-02T11:36:48Z")

</div>

Hi @adhn,

What does “does not work” mean in this context? Is the communication to the ESP32 not working? Or doesn’t the image boot at all?

Guessing now, this is probably a conflict in the UART. Under the hood `u-boot` uses that one, so I can definitely see it either blocking and falling into a boot shell if there is something on the RX line, or failing to init if the UART is not accessible.

The easiest solution to try would be using a different UART. Is that possible?

Greetz,  
Josef