Hi,
The attachments are the rpmsg-tty patches based on linux LTS 5.15.
If you have any problems, feel free to contact me.
Regards,
Bowen Wang
Xiang Xiao 于2024年3月11日周一 23:43写道：
> On Mon, Mar 11, 2024 at 11:13 PM Andre Heinemans
> wrote:
>
> > Hi,
> >
> > Does the NuttX uart_rpmsg.c driver have
meminfo() can be helpful too. It detects many heap corruption problems
(but perhaps not all?). By sprinkling a few calls to kmm_meminfo() in
choice locations, you should also be able to isolate the culprit.
Perhaps after each time the lopri worker runs or after each rpmsg.
On 3/11/2024 1:20
Is there a way to colorize heap to track down the bandid? Like CRC pattern
on all the spaces around and check on every call that the CRC pattern ist
still OK?
Gregory Nutt schrieb am Mo., 11. März 2024, 19:27:
> If the memory location that is corrupted is consistent, then you can
> monitor that
If the memory location that is corrupted is consistent, then you can
monitor that location to find the culprit (perhaps using debug output).
If your debugger supports it then setting a watchpoint could also
trigger a break when the corruption occurs.
Maybe you can also try disabling features
What's needed is some way to binary search where the culprit is.
If I understand correctly, it looks like the crash is happening in the
later stages of board bring-up? What is running before that? Can parts
be disabled or skipped to see if the problem goes away?
Another idea is to try running a s
On Mon, Mar 11, 2024 at 11:13 PM Andre Heinemans
wrote:
> Hi,
>
> Does the NuttX uart_rpmsg.c driver have a Linux counterpart to interact
> with?
Yes, the old version is here:
https://lore.kernel.org/lkml/CAH2Cfb87Wacgsh=xz9h9kgwygbkxnbdbcdj4w3ups2likbt...@mail.gmail.com/
> I want to achieve
Hi,
Does the NuttX uart_rpmsg.c driver have a Linux counterpart to interact with? I
want to achieve a virtual uart connection through rpmsg on an imx8mp between
NuttX (m7) and Linux (a53).
The tty_rpmsg.c driver in mainline linux does not seem compatible as it read
and writes the raw data direc
The reason that the error is confusing is because the error probably did
not occur at the time of the assertion; it probably occurred much earlier.
In most crashes due to heap corruption there are two players: the
culprit and the victim threads. The culprit thread actually cause the
corrupti
