cancel
Showing results for 
Search instead for 
Did you mean: 

Ask for I3C support on NUCLEO-H563ZI (MB1404C)

Alvin0916
Visitor

Hi tech supoort reps,

According to the documentation for the NUCLEO-563ZI (MB1404C), the board is expected to support I3C mode. However, during our evaluation, we were unable to successfully issue I3C shell and CCC (Common Command Code) commands.
At this stage, it is unclear which configuration or setting does not meet the expected requirements.

Could you please provide:
The correct steps to enable and use the I3C interface on this board
Any required software, firmware, or device-tree configurations
A simple example or reference demonstrating successful I3C shell and CCC command execution

Thank you for your support.

[00:00:00.000,000] <inf> i3c_hub_init: I3C Hub I2C init start
[00:00:00.004,000] <inf> i3c_hub_init: Hub I2C init done
[00:00:00.104,000] <inf> i3c_bus_mgr: I3C bus re-enumeration start
[00:00:00.104,000] <inf> i3c_bus_mgr: I3C CCC: RSTDAA
[00:00:00.204,000] <err> i3c_bus_mgr: RSTDAA failed (-116)
*** Booting Zephyr OS build v4.3.0-6019-gef798176ad4c ***
RCC->APB3ENR = 0x00000042
RCC->APB3RSTR = 0x00000000
GPIOB->MODER = 0xfffaaebf
GPIOB->AFR[1] = 0x00000044
GPIOB->OTYPER = 0x00000300
GPIOB->PUPDR = 0x00051100
I3C1->CR = 0x00000000
I3C1->SR = 0x00000000
=== I3C ENTDAA Test Start ===
Issuing ENTDAA (Dynamic Address Assignment)...
ENTDAA timeout (no I3C targets responded)
=== I3C ENTDAA Test Done ===
uart:~$

uart:~$ device list
devices:
- rcc@44020c00 (READY)
DT node labels: rcc
- reset-controller (READY)
DT node labels: rctl
- interrupt-controller@44022000 (READY)
DT node labels: exti
- dma@40021000 (READY)
DT node labels: gpdma2
- dma@40020000 (READY)
DT node labels: gpdma1
- gpio@42022000 (READY)
DT node labels: gpioi
- gpio@42021c00 (READY)
DT node labels: gpioh
- gpio@42021800 (READY)
DT node labels: gpiog
- gpio@42021400 (READY)
DT node labels: gpiof
- gpio@42021000 (READY)
DT node labels: gpioe
- gpio@42020c00 (READY)
DT node labels: gpiod
- gpio@42020800 (READY)
DT node labels: gpioc
- gpio@42020400 (READY)
DT node labels: gpiob
- gpio@42020000 (READY)
DT node labels: gpioa
- serial@44002400 (READY)
DT node labels: lpuart1 arduino_serial
- serial@40004800 (READY)
DT node labels: usart3
- adc@42028000 (READY)
DT node labels: adc1
- i2c@40005400 (READY)
DT node labels: i2c1 arduino_i2c
- i3c@40005c00 (READY)
DT node labels: i3c1
uart:~$

 

uart:~$ devmem dump -a 40005c00 -s 40 -w 8
40005C00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |........ ........|
40005C10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |........ ........|
40005C20: 00 00 00 00 00 00 00 00 |........ |
uart:~$

3 REPLIES 3
mƎALLEm
ST Employee

Hello @Alvin0916 and welcome to the ST community,

 


@Alvin0916 wrote:

Could you please provide:
The correct steps to enable and use the I3C interface on this board
Any required software, firmware, or device-tree configurations
A simple example or reference demonstrating successful I3C shell and CCC command execution


You can refer to the examples provided in the CubeH5 package (running on NUCLEO-H563ZI) over this Github link.

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.
Alvin0916
Visitor

Hi mǝallem,

I have tried using the CubeH5 (HAL/LL) driver with zephyr system,however, it leads to a deadlock condition.


@Alvin0916 wrote:

I have tried using the CubeH5 (HAL/LL) driver with zephyr system,however, it leads to a deadlock condition.


Adding Zephyr into the context makes it a different question here.

Your original question was about the I3C support on NUCLEO-H563ZI.

So the question here: did you try the examples I shared as are? did they work (at least one)? if yes, the original question has been answered.

Adding Zephyr to the context needs from you to open a new post and provide more details about your configuration and Zephyr code.

To give better visibility on the answered topics, please click on "Accept as Solution" on the reply which solved your issue or answered your question.