RTEMS | CTUCANFD Mode Follow-up from "cpukit: add support for common CAN/CAN FD stack" (#5197)

[Gedare Bloom (@gedare)]

Gedare Bloom created an issue: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5197

Assignee: Gedare Bloom

The following discussion from !49 should be addressed:

- [ ] @ppisa started a [discussion](https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/49#note_118423): 

    > I have managed to add FPGA loading for RTEMS to our [LX_CPU](https://www.pikron.com/pages/products/cpu_boards/lx_cpu.html) (NXP LPC4088 + Xilinx XC6SLX9) board RTEMS lpc40xx_ea_ram. It is horrible hack. The single CTU CAN FD IP core fits there only barely in minimal configuration, but I managed stack to send message even when not acknowledged when no other CAN node is present, but I have to change configuration for unacknowledged sending to 
    > ```
    >    mode_reg = ( ctrlmode & CAN_CTRLMODE_PRESUME_ACK ) ?
    > -             ( mode_reg | REG_MODE_SAM ) :
    > -             ( mode_reg & ~REG_MODE_SAM );
    > +             ( mode_reg | REG_MODE_STM ) :
    > +             ( mode_reg & ~REG_MODE_STM );
    > ```
    > There are more options for passing unacknowledged TX (`STM`), self acknowledged (`SAM`, added in later CTU CAN FD versions) etc. But for the `CAN_CTRLMODE_PRESUME_ACK` has `REG_MODE_STM` better match. So I propose this change now or later. It can be discussed even with CTU CAN IP core HDL main author, Ondrej Ille and Jiri Novak, our faculty CAN expert delivering testers for Skoda Auto. But I think that this change is the best option and it is tested.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5197
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250128/3d59043e/attachment.htm>