"SDK - Invalid DAP ACK value: 7" using TE0715-30 with baseboard TEBA0841-02

[hossam84]

Hello John,

I am trying to use TE0715-30 with baseboard TEBA0841-02 -- when I program the TE0715-30 using Vivado hardware manager it works fine and it can detect the ARM_DAP and the PL.
However, when I used SDK it can only program the PL and give me error for PS " Memory write error at 0xF8000114. Invalid DAP IDCODE. Invalid DAP ACK value: 7".

When I use baseboard TE0701-06 everything is nice -- No problem at all. So, I suspect VCCIO Jumpers of the baseboard TEBA0841-02 -- Please correct my setting of the Jumpers if it is wrong.


Attached are:
1- the Vivado hardware manager detection of the ARM_DAP and the PL.
2- Schematic of Jumpers setting
3- My Jumpers setting and
4- error and

Regards,
Hossam

[hossam84]

After many searches and schematic review, I could find why TE0715-30 cannot operate with baseboard TEBA0841-02.

By checking the power rails of the TE0715-30 I noticed that the DDR Power is connected to --> BANK 502 --> (Schematic Name) VCCO_DDR_502 ---> (Voltage) 1.5V
Tracking the VCCO_DDR_502 it is connected to Pin "DDR_PWR" and this Pin is connected to JM2 Pin 19 which is mapped to B2B JB3 Pin 20 (which is not connected to anything)

My conclusion is that:  TEBA0841-02  carrier doesn't support ZYNQ as it doesn't provide power to the DDR (DDR_PWR).

Hope this will help someone else who is may be thinking to integrate ZYNQ with baseboard TEBA0841-02.

Regards,
Hossam

[JH]

Hi,

JM2-19 is an output.
DDR Power will be generated with U3 see schematics page 15.


When does this message appears with JTAG ACK appears? During programming?
Which JTAG programmer did you use? How did you connect the programmer?
Why is you DIP S1-1 from the TEBA0841 carrier on on your picture? This should be off (I think it was off as you has see SoC in Vivado?)
Which external power supply did you use, where did you connect the 3.3V power supply? Some current limit?

You Vivado screenshot shows that PL is programmed.  Design was load from QSPI?

PS:
https://forum.trenz-electronic.de/index.php/topic,1313.msg6259.html#msg6259
--> here it sound like TE0715 was working but not TE0720 and TE0741 on the same TEBA0841. Do you use the same TEBA0841?


br
John

[hossam84]

JM2-19 is an output. DDR Power will be generated with U3 see schematics page 15.


Do you mean it doesn't need to connect with the Pin from TEBA0841-02 baseboard. (See attached)

When does this message appears with JTAG ACK appears? During programming?
Yes, when I run the elf file. (Bitstream is OK)

Which JTAG programmer did you use? How did you connect the programmer?
TE0790-03 -- DIP:  On, Off, Off, Off

Why is you DIP S1-1 from the TEBA0841 carrier on on your picture? This should be off (I think it was off as you has see SoC in Vivado?)
I tested again with TEBA0841 carrier  DIP S1-1 Off and it works.  I changed the TE0790-03 JTAG programmer -- Looks like the other one is malfunctioning.
It seems my observation is wrong ... Sorry

Which external power supply did you use, where did you connect the 3.3V power supply? Some current limit?
I used 3.3V power supply-- I limit the curren to 1A.
You Vivado screenshot shows that PL is programmed.  Design was load from QSPI?
Yes. It was one of my trials and you are right it almost with TEBA0841 carrier  DIP S1-1 Off.
PS:
https://forum.trenz-electronic.de/index.php/topic,1313.msg6259.html#msg6259
--> here it sound like TE0715 was working but not TE0720 and TE0741 on the same TEBA0841. Do you use the same TEBA0841?
For bitstraem programming there is no problem using TE0715-30 with baseboard TEBA0841-02.
The issue appeared when I tried to run the *.elf file from the SDK.

Thanks for your clarification... 

Regards,
Hossam

[JH]

Hi,

Do you mean it doesn't need to connect with the Pin from TEBA0841-02 baseboard. (See attached)

No not needed on carrier.

I tested again with TEBA0841 carrier  DIP S1-1 Off and it works.  I changed the TE0790-03 JTAG programmer -- Looks like the other one is malfunctioning.
It seems my observation is wrong ... Sorry

OK.

Maybe this TE0790 was also the problem with your TE0720 and TE0741?  The behaviour was different but I have no explanation for your problem with TE0720 and TE0741 on the carrier.

br
John