eeeck/CANdigger
1
0
Fork 1
Code Issues 7 Pull Requests 1 Actions Projects 1 Releases 6 Wiki Activity

Place Time-Critical Data in CCMRAM #9

New Issue
Closed
opened 2026-06-14 16:37:10 +02:00 by eeeck · 2 comments
eeeck commented 2026-06-14 16:37:10 +02:00
Owner
Copy Link
Copy Source

Place CAN message queues (xCAN1RxQueue, xCAN2RxQueue) into the CCM, which is directly connected to the core and is ideal for real time message queues.

Place CAN message queues (xCAN1RxQueue, xCAN2RxQueue) into the CCM, which is directly connected to the core and is ideal for real time message queues.
eeeck added the enhancement label 2026-06-14 16:37:10 +02:00
eeeck self-assigned this 2026-06-14 16:37:10 +02:00
eeeck added the experimental label 2026-06-14 16:42:49 +02:00
eeeck commented 2026-06-14 16:44:14 +02:00
Author
Owner
Copy Link
Copy Source
  • Add CCMRAM to Memory Regions in STM32F405RGTx_FLASH.l
  • Create a New Section for CCM Variables
  • Use the __attribute__((section(".ccmram"))) specifier to place data
- [ ] Add CCMRAM to Memory Regions in STM32F405RGTx_FLASH.l - [ ] Create a New Section for CCM Variables - [ ] Use the ```__attribute__((section(".ccmram")))``` specifier to place data
eeeck added this to the Thesis SCRUM project 2026-06-14 16:51:06 +02:00
eeeck moved this to In Progress in Thesis SCRUM on 2026-06-16 01:00:21 +02:00
eeeck added reference dev_ccram 2026-06-16 01:01:15 +02:00
eeeck moved this to Done in Thesis SCRUM on 2026-06-16 01:40:31 +02:00
eeeck closed this issue 2026-06-16 01:40:35 +02:00
eeeck commented 2026-06-16 01:41:29 +02:00
Author
Owner
Copy Link
Copy Source

Done in 88e13e610328d53078bb42cbbe8074155ff42c2b (branch dev_ccram)

Done in 88e13e610328d53078bb42cbbe8074155ff42c2b (branch dev_ccram)
eeeck moved this to To Do in Thesis SCRUM on 2026-06-16 22:44:42 +02:00
eeeck moved this to Done in Thesis SCRUM on 2026-06-16 22:46:08 +02:00
Sign in to join this conversation.
dev_ccram
Branches Tags
Labels
Clear labels
bug
Something is not working
 docs
Documentation related issue
 enhancement
Enchancement on an existing feature
 experimental
Experimental stuff
 feature
A new feature
 hardware
Hardware related issue
 invalid
Something is wrong
 minor
Small changes
 not planned
Feature not planned
 test
Testing/flashing related issues
No Label enhancement experimental
Milestone
No items
No Milestone
Projects
Clear projects
No project Thesis SCRUM
Assignees
Clear assignees
eeeck (Erick)
No Assignees eeeck
1 Participants
Notifications
Due Date
No due date set.
Blocks
#19 WIP: Isolate CAN FreeRTOS stacks and queues in CCMRAM to eliminate future DMA bus contention
eeeck/CANdigger
Reference: eeeck/CANdigger#9
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?