Recent posts

#11

UltraScale / Re: TE0865-02+TEBT0865+KK0865

Last post by mer - June 05, 2025, 05:47:47 PM

Ok, thanks for the reply. Let me ask this then, do you have a schematic/documentation for the little JTAG/UART board that is plugged into JB1 on the carrier? There are a couple switches on there that I'm not sure what they do. Thanks.

#12

UltraScale / Re: TE0865-02+TEBT0865+KK0865

Last post by Antti Lukats - June 05, 2025, 10:24:03 AM

TEBT0865 is TEST basis (the second T stands for TEST) to just test TE0865 is alive. It was designed much earlier than KK0865, hence there is no PWM Fan header on this board. The design support for TEBT0865 is currently limited to Schematic that is available from downloads.

#13

Trenz Electronic FPGA Modules / Re: TE0701 / TE0711 UART Pins

Last post by Antti Lukats - June 05, 2025, 10:16:45 AM

Hi,
all you need is to read the TE0701 TRM, it is all explained there:

https://wiki.trenz-electronic.de/display/PD/TE0701+TRM

There is a diagram that shows that the CPLD is "forwarding" the UART pins, and a bit later is defined to WHAT pins the forwarding is done. So all the information you need is there.

#14

Trenz Electronic FPGA Modules / TE0701 / TE0711 UART Pins

Last post by haraldmz - June 05, 2025, 09:52:12 AM

Where do I find which pins on JB1 the UART lines are connected to? The TE0701 TRM chap. 5.2 says "UART RX", "UART TX" on JB1, but such pin names do not exist on TE0701 JB1. I tried to get a clue from reading the schematics but the trace ends at CLPD BDBUS0 and 1 (which _may_ be the correct pins but the TRM chap. 6.2 does not state this clearly). But the BDBUS pins aren't available on JB1 anyway.

So what gives?

#15

UltraScale / TE0865-02+TEBT0865+KK0865

Last post by mer - June 04, 2025, 11:42:27 PM

Hello, beginning to put together as system utilizing TE0865-02+TEBT0865+KK0865. Noticing that the TEBT0865 TRM is empty. Am I looking in the wrong place? https://wiki.trenz-electronic.de/display/PD/TEBT0865
Also, there doesn't seem to be an obvious place to plug in the KK0865 pwm fan. Little help?

#16

UltraScale / Re: Support Request for TE0808...

Last post by JH - June 02, 2025, 08:50:31 AM

Hi,
bitstream itself does not configure PS. This will be done by FSBL, not with bitstream.This is the reason why you didn't see any VIO core, because CLK is missing. In case you want to use PS-PL CLKs and you need only PL part, boot system with your configured PS from SD Card (You can use our prebuilt Boot.bin in case you use the same CLKs like we in our reference design) and overwrite PL over JTAG like you has done above.
br
John

#17

Trenz Electronic FPGA Modules / Re: sys_clk IOSTANDARD for TE0...

Last post by bggardner - May 30, 2025, 05:45:23 PM

Thank you.  The sys_clk input (somehow) still works using LVCMOS33, but also works with your suggested changes.  For the benefit of others, I replaced

set_property -dict {PACKAGE_PIN T14 IOSTANDARD LVCMOS33} [get_ports sys_clk]

with

set_property INTERNAL_VREF 0.9 [get_iobanks 14]
set_property -dict {PACKAGE_PIN T14 IOSTANDARD SSTL18_I} [get_ports sys_clk]

#18

Trenz Electronic FPGA Modules / Re: sys_clk IOSTANDARD for TE0...

Last post by Antti Lukats - May 30, 2025, 12:07:53 PM

It is documentation XDC issue, please select SSTL18_I as IO Standard, after that you need open device constraints windows and use mouse to drop the IO Bank 14 to "0.9V" this will enable internal VREF.

Then it should work.

#19

UltraScale / Re: First "Hello World" - JTAG...

Last post by Antti Lukats - May 30, 2025, 11:32:07 AM

Hi Meik,

Please try downloading and installing the latest USB to JTAG converter driver from the manufacturer's website:

https://ftdichip.com/products/ft2232h-56q/

This may help resolve the JTAG-related issues you're experiencing.

I do not think that the issue is related to FTDI drivers. The JTAG seems to work OK.

#20

UltraScale / Re: Support Request for TE0808...

Last post by Antti Lukats - May 30, 2025, 11:30:36 AM

your report already says what the likely issue is, namly if the VIO core does not see a free running clock, it will not be detected. So it is a clocking issue.