Sven Ginka

`apt install libglib2.0-dev ` fixes this issue for me.

@henrikbrixandersen from the source it looks like you are the expert on `can_sam.c` did you notice anything or could you confirm seeing can messages at a can-sniffer tool in general...

it looks like this is can_sam specific. the offset register for the message ram offset is by default `REG_CCFG_CAN0` = `0x20400000` however the driver comes up with `sam_cfg->mram` = `0x2041b40`....

> the driver comes up with `sam_cfg->mram` = `0x2041b40` @henrikbrixandersen I am curious where this value comes from. its not the initial value. why should that be changed in first...

> Please retest this on the `v3.5-branch` (making sure commit [8415778](https://github.com/zephyrproject-rtos/zephyr/commit/8415778a1a04bab98f10523fe4ca1894c79e41f5) is included in your branch when testing). Testing on `main` would also be nice. Please note that I **already...

the DMA base address (where the ATMEL controller expects the MCAN memory) for CAN0 is by default `0x2040 0000` * debugging the controller with the current zephry-3.5 can-driver gives me...

just wondering if there is a more easy solution: `can_sam.c` is calling [here](https://github.com/zephyrproject-rtos/zephyr/blob/a48c958c8fb85a0985880482df9c79407a8fc55e/drivers/can/can_sam.c#L104) ``` can_mcan_configure_mram(dev, 0U, sam_cfg->mram); ``` where we expect the DMA base address ([here](https://github.com/zephyrproject-rtos/zephyr/blob/a48c958c8fb85a0985880482df9c79407a8fc55e/drivers/can/can_mcan.c#L1241)): ``` int can_mcan_configure_mram(const struct...

so actually my [PR](https://github.com/zephyrproject-rtos/zephyr/pull/69405) is almost ready. problem is that this of course works only for CAN0 and not CAN1 because CAN0 mcan segment address is in `REG_CCFG_CAN0` where CAN1...

Nice, I will prepare,...

It looks like there are 2 options: option 1: "standalone config" ``` can0: can@40030000 { compatible = "atmel,sam-can"; reg = ; dma-base-reg = ; ... }; ``` option 2: "extending...