# Use libcanard to send getinfo responce problem

**URL:** <https://forum.opencyphal.org/t/use-libcanard-to-send-getinfo-responce-problem/2371>\
**Category:** Libcanard\
**Created:** [April 30, 2025, 1:32am UTC](https://forum.opencyphal.org/t/use-libcanard-to-send-getinfo-responce-problem/2371 "2025-04-30T01:32:42Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [May 8, 2025, 3:24pm UTC](https://forum.opencyphal.org/t/use-libcanard-to-send-getinfo-responce-problem/2371/4 "2025-05-08T15:24:55Z")

</div>

Your code looks correct. The transfer also looks correct, the “garbage bytes” are the transfer-CRC. You need to add error handling to the TxPush function and then look into the part that offloads the CAN frames from the TX queue into the CAN driver.

If you’re using the stock CAN driver from ST, you need to be sure to avoid inner priority inversion:

> [@UAVCAN/CAN: tx buffer management in CAN (FD) controllers](https://forum.opencyphal.org/t/uavcan-can-tx-buffer-management-in-can-fd-controllers/1215):
>
> tl;dr: do not rely on the tx buffer management services provided by your CAN controller. Make your driver manage the transmission order in software instead. Otherwise, you will run into either a priority inversion problem or data loss caused by frame reordering. I just ran a quick survey of the TX buffer management capabilities offered by the following products: [TI TCAN4550](https://www.ti.com/product/TCAN4550) — standalone CAN FD controller chip [Microchip ATSAM D5x/E5x](https://www.microchip.com/wwwproducts/en/ATSAME51N19A) (FD-capable) FDCAN & bxCAN macrocells by ST Microelectroni…

---

_[View the full topic](https://forum.opencyphal.org/t/use-libcanard-to-send-getinfo-responce-problem/2371)._
