Skip to main content
Visitor II
June 19, 2025
Question

STM32 H563ZI as I3C target does not respond to DAA CCC

  • June 19, 2025
  • 1 reply
  • 346 views

Hello,

 

I have 2 NUCLEO-H563ZI boards connected to each other as required, one running the "I3C_Target_Private_Command_IT" example and the other running the "I3C_Controller_Private_Command_IT", i also have a logic analyzer connected to monitor the I3C communications, however the setup is not working as expected, the "target"  ACKs the initial broadcast from the "controller", but NACKs the subsequent broadcast after the "ENTDAA" CCC

 

mnhaggag_0-1750363693889.png

Any thoughts on what could be wrong here ? I tried debugging but the "target" board simply does not seem to be observing any interrupts/events during this whole "ENTDAA" CCC transmission from the "controller"

    This topic has been closed for replies.

    1 reply

    ST Employee
    June 20, 2025

    Hello @mnhaggag ,

     

     - Use short wire as possible between the boards to help communication at 12.5Mhz.(make sure that you are using the correct pins)
     - Connect GND of Controller board to GND of Target Board.
    Run the Controller before run the Target, this will let a false startup phase on Target side as there is no high level on the bus, if the Target is started before the Controller.

    Let me know! ;) 

    Thank you!
    Foued
    mnhaggagAuthor
    Visitor II
    July 3, 2025

    I did all of that, and I still don't see the setup working as expected, I either get a slow blinking LED on the controller board or the target board (indicating an error), and if I use the debugger to check the aRxbuffer on either board, I can see that the example did not work properly (missing or no RX bytes received)

     

    Below is a sample of the logic analyzer capture after the first button press (the DAA process)

     

    mnhaggag_1-1751560680513.png

    Below is a sample of the logic analyzer capture after the second button press

    mnhaggag_2-1751560720563.png

    As you can see, the write sequence after the second button press is "rejected" as the target doesn't ACK the address

     

    Any thoughts ?