Re: [PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

>The CAN bus changes have warnings ... > >In file included from ../../../cpukit/include/dev/can/canqueueimpl.h:48, >from ../../../cpukit/dev/can/can.c:45: >../../../cpukit/dev/can/can.c: In function 'can_bus_read': >../../../cpukit/dev/can/can.c:213:15: warning: format '%u' expects

Hands up, do you use the Mini Robomind BSP (MRM332)?

Hi all, The Mini Robomind is a board that was available through the Seattle Robotics Society that used the Motorola MC68332 processor. The BSP is called MRM332. I was wondering if anybody uses this BSP, either for a Mini Robomind or as a basis for some other MC68332 board? Why? I was talking

Hands up, do you use the Mini Robomind BSP (MRM332)?

Hi all,The Mini Robomind is a board that was available through the Seattle Robotics Society that used the Motorola MC68332 processor. The BSP is called MRM332.I was wondering if anybody uses this BSP, either for a Mini Robomind or as a basis for some other MC68332 board?Why? I was talking with

Moving ticket milestones to a different RTEMS version

Hi, Joel and I have been cleaning up the 6 tickets and some have been moved to 7 (thanks) which may be appropriate however I am wondering about open ended tickets for a specific set of work and release notes. These tickets are really great for collecting commits for a specific change. The

Re: [PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

On 2/12/2022 2:38 pm, Chris Johns wrote: > The CAN bus changes have warnings ... > > In file included from ../../../cpukit/include/dev/can/canqueueimpl.h:48, > from ../../../cpukit/dev/can/can.c:45: > ../../../cpukit/dev/can/can.c: In function 'can_bus_read': >

Re: [PATCH] cpukit/include/dev/can: Disabled debug prints in CAN Framework

The CAN bus changes have warnings ... In file included from ../../../cpukit/include/dev/can/canqueueimpl.h:48, from ../../../cpukit/dev/can/can.c:45: ../../../cpukit/dev/can/can.c: In function 'can_bus_read': ../../../cpukit/dev/can/can.c:213:15: warning: format '%u' expects

Re: New RISC-V BSP variant (Kendryte K210)

On Thu, Dec 1, 2022 at 6:06 PM Joel Sherrill wrote: > > I'm going to say enthusiastically yes. > > I suspect that other boards will be very similar so this is likely a good > basis to go from. > > If you have links where it is actually for sale and not just described, that > would be great.

Request for Coverity Issue Review

Hi As we approach a release branch, it would be helpful if 1+ persons would kindly volunteer to see if they can kill some of the Coverity reported issues. I admit I haven't looked at them this week. I'm busy killing tickets before 6. :) Help appreciated. Thanks. --joel

Request for comments on more BSP or architecture port deprecations

Hi As we head toward a release branch, it is time to once again ask if anything else should be deprecated in 6. We currently have sh, sparc64, and v850 marked for deprecation. That means they will be included in 6 but removed from the master soon after branching. Any others living on borrowed

Re: New RISC-V BSP variant (Kendryte K210)

I'm going to say enthusiastically yes. I suspect that other boards will be very similar so this is likely a good basis to go from. If you have links where it is actually for sale and not just described, that would be great. Chris would likely encourage you to post rtems-tester results. :) And

Re: [PATCH 0/3] Add CONFIGURE_RECORD_INTERRUPTS_ENABLED

Looks good. Thanks Chris On 1/12/2022 11:10 pm, Sebastian Huber wrote: > This enables the tracing of interrupt entry/exit events through an > application configuration option. The interrupt processing can be > viewed with Trace Compass. > > Sebastian Huber (3): > bsps/irq: Rename handler in

Re: [PATCH] Document CONFIGURE_RECORD_INTERRUPTS_ENABLED

Looks good. Thanks Chris On 1/12/2022 11:11 pm, Sebastian Huber wrote: > Close #4769. > --- > c-user/config/event-record.rst | 43 +- > user/tracing/eventrecording.rst | 65 +++-- > 2 files changed, 47 insertions(+), 61 deletions(-) > > diff

New RISC-V BSP variant (Kendryte K210)

Hi, I have been working on a basic BSP for the Kendryte K210 RISC-V CPU, and I was wondering if the community members would like me to submit it. The Kendryte K210 is a dual core 64 bit RISC-V processor with a wealth of peripheral I/O, a built-in AI NPU, and 8 Megabytes of on-chip SRAM. I like it

[PATCH rtems-docs] c-user: Add Local vs Global to Key Concepts Chapter

Add multiple new index entries and cite them where RTEMS_LOCAL and RTEMS_GLOBAL are cited. Closes #4453. --- c-user/key_concepts.rst | 78 - c-user/message/directives.rst | 5 +++ c-user/partition/directives.rst | 5 +++

RTEMS Open Class (virtual) January 23-27, 2023

Hi There will be an RTEMS Open Class held virtually the week of January 23-27. Times each day will be based on the US Central time zone (Chicago). Adjustments may be considered to accommodate the participants. January 23 - Kick Start and Getting Started January 24-27 - Open Class Details and

Re: [PATCH 0/3] Add CONFIGURE_RECORD_INTERRUPTS_ENABLED

On 01.12.22 15:54, Joel Sherrill wrote: Is there anything the BSP has to do to support this? Yes, it should use the generic interrupt controller support (../../objirq). What about the patch (in the docs?) to add records for arm? Is it obsolete? I assume I just haven't noticed a

Re: [PATCH 0/3] Add CONFIGURE_RECORD_INTERRUPTS_ENABLED

Is there anything the BSP has to do to support this? What about the patch (in the docs?) to add records for arm? Is it obsolete? I assume I just haven't noticed a documentation patch for the configure option. --joel On Thu, Dec 1, 2022 at 6:11 AM Sebastian Huber <

[PATCH] Document CONFIGURE_RECORD_INTERRUPTS_ENABLED

Close #4769. --- c-user/config/event-record.rst | 43 +- user/tracing/eventrecording.rst | 65 +++-- 2 files changed, 47 insertions(+), 61 deletions(-) diff --git a/c-user/config/event-record.rst b/c-user/config/event-record.rst index

[PATCH 2/3] bsps/irq: Add bsp_interrupt_get_dispatch_table_slot()

Update #4769. --- bsps/include/bsp/irq-generic.h| 11 +++ bsps/shared/irq/irq-entry-remove.c| 2 +- bsps/shared/irq/irq-generic.c | 19 +-- bsps/shared/irq/irq-handler-iterate.c | 2 +- 4 files changed, 26 insertions(+), 8 deletions(-) diff --git

[PATCH 1/3] bsps/irq: Rename handler in dispatch table

The name handler table was a bit misleading after the last rework. Rename it in distach table. Update the documentation accordingly. Update #4769. --- bsps/include/bsp/irq-generic.h| 68 +-- bsps/powerpc/mpc55xxevb/include/bsp/irq.h | 2 +-

[PATCH 0/3] Add CONFIGURE_RECORD_INTERRUPTS_ENABLED

This enables the tracing of interrupt entry/exit events through an application configuration option. The interrupt processing can be viewed with Trace Compass. Sebastian Huber (3): bsps/irq: Rename handler in dispatch table bsps/irq: Add bsp_interrupt_get_dispatch_table_slot() config: Add

[PATCH 3/3] config: Add CONFIGURE_RECORD_INTERRUPTS_ENABLED

Update #4769. --- bsps/shared/irq/irq-record.c | 97 ++ cpukit/doxygen/appl-config.h | 23 + cpukit/include/rtems/confdefs/extensions.h | 8 ++ cpukit/include/rtems/record.h | 2 + spec/build/bsps/objirq.yml | 1 +