Hello,
We are using Nuttx and its SocketCAN support (on top of iMXRT hardware), but
have run into some problems related to packet reordering and also possible
soft-locks/stalls in the rx side.
The symptoms we have is that the upper layer, which is a isotp implementation,
receives packets out
Hi Marten,
The IMXRT SocketCAN driver is based on the S32K1XX driver which had limited
amount of mailboxes.
So they had to be cleared as quick as possible to make sure we don't drop
packets if all mailboxes get full.
On the IMXRT it's different since in non-FD mode you've got a lot of mailboxes
Thanks for your input Peter,
> The IMXRT SocketCAN driver is based on the S32K1XX driver which had limited
> amount of mailboxes.
> So they had to be cleared as quick as possible to make sure we don't drop
> packets if all mailboxes get full.
I did get that from the git history, however I hope w
Thanks Bartok. Seems, as usual, I am Mr. DumbHead as I am already using a
CortexA5.svd file and do, indeed, see Cortex registers. But IO am not 100%
convinced the svd is totally right so I'm trying to track one down for the
SAMA5D2 family.
What I can't do is trace the cause of an exception. The
Hello world :-)
There is a platform support update request on RISC-V tech mailinglists
(see forward below).. on the referenced site I can see that NuttX is
marked "IN PROGRESS".. but I know some chips can now run NuttX on RV
cores pretty well (I used ESP32-C3 myself and heard that Microchip
joined
Hi,
ESP32-C3 worked perfectly out-of-the-box for me so I guess it is "fully
supported"
Sebastien
Le 03/03/2023 à 15:48, Tomek CEDRO a écrit :
Hello world :-)
There is a platform support update request on RISC-V tech mailinglists
(see forward below).. on the referenced site I can see that Nu
Hi Tomek,
Nice finding. Actually NuttX on RISC-V is already used on commercial
products from at least one big company, so I suggest it should be
Fully Supported.
BR,
Alan
On 3/3/23, Tomek CEDRO wrote:
> Hello world :-)
>
> There is a platform support update request on RISC-V tech mailinglists
On Fri, Mar 3, 2023 at 5:10 PM Alan C. Assis wrote:
> Hi Tomek,
> Nice finding. Actually NuttX on RISC-V is already used on commercial
> products from at least one big company, so I suggest it should be
> Fully Supported.
ACK! Is both riscv32 and riscv64 ISA supported or only one of them? :-)
--
On Fri, Mar 3, 2023 at 5:18 PM Tomek CEDRO wrote:
>
> On Fri, Mar 3, 2023 at 5:10 PM Alan C. Assis wrote:
> > Hi Tomek,
> > Nice finding. Actually NuttX on RISC-V is already used on commercial
> > products from at least one big company, so I suggest it should be
> > Fully Supported.
>
> ACK! Is bot
Both are supported.
On 3/3/23, Tomek CEDRO wrote:
> On Fri, Mar 3, 2023 at 5:10 PM Alan C. Assis wrote:
>> Hi Tomek,
>> Nice finding. Actually NuttX on RISC-V is already used on commercial
>> products from at least one big company, so I suggest it should be
>> Fully Supported.
>
> ACK! Is both ri
On Fri, Mar 3, 2023 at 5:23 PM Alan C. Assis wrote:>
> Both are supported.
ACK :-) Update request to mark "FULLY SUPPORTED" has been sent :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Hi all,
The bug I thought I had in a driver I'm developing (well, one of them!) appears
to be related to file closing.
- I have a related example-type app I'm using to exercise and check the driver.
It opens 2 "files" (O-RDONLY) to read data from the device driver
- I have enabled CONFIG_SIGKIL
On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
> The bug I thought I had in a driver I'm developing (well, one of them!)
> appears to be related to file closing.
>
> - I have a related example-type app I'm using to exercise and check the
> driver. It opens 2 "files" (O-RDONLY) to read data f
On 3/3/2023 12:36 PM, Nathan Hartman wrote:
On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
The bug I thought I had in a driver I'm developing (well, one of them!) appears
to be related to file closing.
- I have a related example-type app I'm using to exercise and check the driver. It open
>From: Nathan Hartman
>Sent: 03 March 2023 18:36
>To: dev@nuttx.apache.org
>Subject: Re: Help me understand file open/close behaviours?
>
>On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
>> The bug I thought I had in a driver I'm developing (well, one of them!)
>appears to be related to file c
On 3/3/2023 12:56 PM, Gregory Nutt wrote:
On 3/3/2023 12:36 PM, Nathan Hartman wrote:
On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
The bug I thought I had in a driver I'm developing (well, one of
them!) appears to be related to file closing.
- I have a related example-type app I'm usin
>From: Gregory Nutt
>Sent: 03 March 2023 19:03
>To: dev@nuttx.apache.org
>Subject: Re: Help me understand file open/close behaviours?
>
>On 3/3/2023 12:56 PM, Gregory Nutt wrote:
>> On 3/3/2023 12:36 PM, Nathan Hartman wrote:
>>> On Fri, Mar 3, 2023 at 1:07 PM Tim Hardisty wrote:
The bug I t
Interesting:
https://news.slashdot.org/story/23/02/26/1950212/who-writes-linux-and-open-source-software
I've often complained on list about the near disappearance of individual
contributors to the OS. It was created by individual contributors and
most of the early, critical designs came fro
18 matches
Mail list logo
