SWD Init sequence with E2-Lite

Hello,

Does the SWD connection between E2 Lite and RA works fine or do you have any issues when connecting ?

The strapwire prototype has issue, it hangs with the states above (res low, swdio high, swclk high), for 500ms until the E2 Lite declares non response.

Is the SWD init sequence the 1bit type, is it possible to have more insights on the initialization sequence.

Thanks & regards
Jean-François

Please provide for review your schmematics of connections between E2 Lite and RA board. I have shared the relevant document guides on the previous thread you posted:

community.renesas.com/.../cannot-flash-firmware-on-ra4-swd

In the strapwire
  The Vcl is on a 4.7uF
  /Reset is pulled up
  MD is pulled up internally (booting standalone)
  Swdio/Clk on the SWD interface

So these signals are fixed per RA4M1 manual indeed.

I'm just trying understand from the states defined in first post above, do we have enough informations to determine if the MCU has failed which is possible due to previously wrong wiring.

I.e. these two highlights :

• Is the MCU going to pull a line as part of init sequence, on oscilloscope, i observe nothing on both lines
• Is it normal the Flasher keeps /Reset low ?

In the strapwire
  The Vcl is on a 4.7uF
  /Reset is pulled up
  MD is pulled up internally (booting standalone)
  Swdio/Clk on the SWD interface

So these signals are fixed per RA4M1 manual indeed.

I'm just trying understand from the states defined in first post above, do we have enough informations to determine if the MCU has failed which is possible due to previously wrong wiring.

I.e. these two highlights :

• Is the MCU going to pull a line as part of init sequence, on oscilloscope, i observe nothing on both lines
• Is it normal the Flasher keeps /Reset low ?

Are you able to connect with Renesas Flash Programmer ?

No it is as mentionned in original post above that is :

Next, when i initiate "Connect", we have:

• SWDIO high
• SWCLK high
• 500 ms pass, then Device not responding
  
  The flasher gives "Device not responding", which is why i probed all signals and am trying to figure out some informations from these. So i would like understand these 2 points, about /Reset behavior from E2 Lite and the first thing that should happen on the swdio/clk lines for a properly working mcu.

Regards

Jean-François

To make sure if the device has been electrically damaged or the SWD interface is still not usable, I recommend to implement the SCI connections to boot the device in boot mode and try to erase it. If this fails then it is likely that the device has been electrically damaged.

Please refer to chapter 2.4.2 or 2.4.4

www.renesas.com/.../e2-emulator-e2-emulator-lite-additional-document-users-manual-notes-connection-ra-devices

Yes indeed,

That was checked, i have 2 Renesas E2 Lite, both are "Pass" with the SCI tool so this is all ok.
Measurement show same behavior with both tools.

Jean-François

I am not talking about the Self Check tool. I am talking about booting the device in boot mode via SCI (SCI boot mode). 

Ok, it is not implemented in HW.

Could we get to the 2 points i highlighted initially ? That would just let me briefly get to understand the issue.

Other points i'll handle them, it's just these 2 questions i had at this moment.

Regards

Jean-François

Appendix 1. Port States in Each Processing Mode mentions the status of each port during reset state.

https://www.renesas.com/en/document/mah/renesas-ra4m1-group-users-manual-hardware?r=1054146

I am not aware of any documentation describing the levels of signals during SWD connection.

Ok, i'll dig in.
Regards
Jean-François