Recent Posts

Pages: 1 [2] 3 4 ... 10
Trenz Electronic FPGA Modules / Re: TE7012 PetaLinux Ethernet problem
« Last post by JH on November 04, 2022, 08:02:11 AM »
can you send me the serial number of your module and your carrier. It's on the small sticker with QR code on the boards.
Trenz Electronic FPGA Modules / TE-0821 I2C interfaces
« Last post by Vesku_Koo on November 03, 2022, 10:11:13 PM »

we need to communicate external sensors via I2C interface. The TE-0821 module's I2C isn't routed out of the module. However, i got the impression that the SoC on board contains another I2C controller, is that correct? If so, can SDA and SCL signals be routed to any free MIO pins?

Trenz Electronic FPGA Modules / Re: TE7012 PetaLinux Ethernet problem
« Last post by Waldi3141 on November 03, 2022, 02:42:25 PM »
Hi again,

sorry it is hard to figure out exactly what your problem is with given information.
From the Boot log i would say it is a software problem since it says "link is up".
When you plug the board to your network switch, do you see anything on the other end? Like a new device on the network?
What you do see when you type "ifconfig" in petalinux on the board?

best regards

UltraScale / Upgrade Toolchain 2019.2 to 2021.2: Petalinux Build Errors
« Last post by ZynqMPuser on November 03, 2022, 02:00:49 PM »
I was using the TE0808 ZynqMP on the TEBF0808 Carrier for quite some time with the 2019 toolchain and the Petalinux-Workflow worked fine with various changes in the device trees etc. The system is running with FPGAcode, a RPU baremetal application and an APU Petalinux.
Now I set up the 2021.2 toolchain according to your Petalinux KICKstart and tried to port my project.
That included:
- set up the new FPGA .xsa design in Vivado 2021.2
- set up the complete 2021.2 Petalinux toolchain in my VMware
- do the same changes (as available since there are some changes) in the various petalinux-config menues
- I DID NOT download all the sstate_cache and downloads but i thought it also works directly online; or is it specifically needed to download and include all these files?

But in the last step "petalinux-build", I always end up with the same error that seems to be in the u-boot part.

ERROR: u-boot-xlnx-v2021.01-xilinx-v2021.2+gitAUTOINC+63b6d260db-r0 do_compile: oe_runmake failed
ERROR: u-boot-xlnx-v2021.01-xilinx-v2021.2+gitAUTOINC+63b6d260db-r0 do_compile: Execution of '/"projectpath"/build/tmp/work/zynqmp_generic-xilinx-linux/u-boot-xlnx/v2021.01-xilinx-v2021.2+gitAUTOINC+63b6d260db-r0/temp/run.do_compile.8977' failed with exit code 1
ERROR: Task (/"projectpath"/components/yocto/layers/meta-xilinx/meta-xilinx-bsp/recipes-bsp/u-boot/ failed with exit code '1'

Due you have any clue where/how to tackle these error messages?
I didn't expect too many problems in just porting to a newer version :(

Thanks a lot in advance,
Trenz Electronic FPGA Modules / Re: TE0720 power debug after incorrectly applying voltage.
« Last post by JH on November 02, 2022, 06:47:12 AM »
CPLD Firmware documentation:

But when you say all 4 leds are blinking...I would say module is damaged, looks like it restarts very time.

Green LED D4 is Done LED (Indicates PL Part is Programmed or not):

When you change boot mode to SD an power on without SD, it should be stay on. Is it on in this case or still blinking.
In any case I think something is damaged on the module.
I have a TE0720 XC7Z020 chip connected to to the TE0703-06 Carrier.

In my system I plugged in a cable incorrectly and blew U3 on the carrier, verified with a thermal camera  :(. Hoping to salvage, I took the TE0720 off and plugged it into a new carrier. Now instead of getting by the flashing red on the TE0720 it is a solid red, and instead of D3 and D4 on the TE0703 being solid, all of D1, D2, D3, and D4 are blinking slowly. I am not able to connect to the device though JTAG. When I swap this out with a different chip (TE0720-04-31C33MA) on the same carrier behavior goes back to normal.

Wondering what this indicates, and hoping to salvage. I don't have any spares of my part.

Would appreciate any help or insights.
EDDP-EDPS Support / Re: problem when run Vivado HLS example
« Last post by Jason bourne on November 01, 2022, 06:15:18 AM »
If you want to generate IP cores through HLS, add solution to the current project so that you can compile and generate ip cores.
can you send me the exact serial number of your modules with the ETH Problem?
Maybe they are effected on this AVN;

Can you send the serial numbers to ""
can you send me the serial numbers of your both modules. It's the number on small sticker with qr code.
I'm having multiple Trenz TE0802-2 evaluation boards at my desk (some with serial no. 6581XX which seem to work fine, some with serial no. 6998XX which having my issue).

I created a bootable SD card image (configured & built PetaLinux 2021.2). The system is booting successfully.
Then I connected the Trenz board to my PC Network Interface Card (NIC, which is a Intel(R) Ethernet Connection (7) I219-LM).
The Ethernet link comes up, ETH-connection is established, after some time the link is falling down, without any interaction from my side (e.g. disconnecting the Eth-cable), it comes up again, falling down, and so on.

- I tested with several different network cables, also brand new ones
- I checked already my "faulty" boards with SD card images from colleagues = my boards still having link drops
- My colleagues tested my image on their board = they having no link drops on their boards
- So it should not be related to a special kernel configuration or device tree modification
- How it looks like on the console you will find at the end of the following log:

Code: [Select]
Configuring network interfaces... [    9.270684] macb ff0e0000.ethernet eth0: PHY [ff0e0000.ethernet-ffffffff:01] driver [Marvell 88E1510] (irq=POLL)
[    9.280933] macb ff0e0000.ethernet eth0: configuring for phy/rgmii-id link mode
[    9.289560] pps pps0: new PPS source ptp0
[    9.293719] macb ff0e0000.ethernet: gem-ptp-timer ptp clock registered.
udhcpc: started, v1.32.0
udhcpc: sending discover
udhcpc: sending discover
[   13.393562] macb ff0e0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   13.401304] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udhcpc: sending discover
udhcpc: no lease, forking to background
Starting haveged: haveged: command socket is listening at fd 3
haveged: haveged starting up

Starting Dropbear SSH server: dropbear.
starting Busybox HTTP Daemon: httpd... done.
Starting internet superserver: inetd.
Starting syslogd/klogd: done
Starting tcf-agent: [   19.317283] random: crng init done

PetaLinux 2021.2 te0802_os ttyPS0

root@te0802_os:~# ethtool eth0
Settings for eth0:
        Supported ports: [ TP    MII     FIBRE ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: Transmit-only
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: Transmit-only
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: No
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Auto-negotiation: on
        Port: MII
        PHYAD: 1
        Transceiver: external
        Link detected: yes
root@te0802_os:~# ifconfig
eth0      Link encap:Ethernet  HWaddr E8:EB:1B:12:91:27
          inet6 addr: fe80::eaeb:1bff:fe12:9127/64 Scope:Link
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1890 (1.8 KiB)  TX bytes:3184 (3.1 KiB)

lo        Link encap:Local Loopback
          inet addr:  Mask:
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@te0802_os:~# [  118.863098] macb ff0e0000.ethernet eth0: Link is Down
[  120.912611] macb ff0e0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[  165.967130] macb ff0e0000.ethernet eth0: Link is Down
[  169.040606] macb ff0e0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[ 1222.735104] macb ff0e0000.ethernet eth0: Link is Down
[ 1225.808612] macb ff0e0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off

- maybe it is linked to the assembled Marvell 88E1512-NNP2 chip, which divers on my boards:

1x working board has a Marvell chip designated:
2112 A0P --> Year 21 Week 12

4x faulty boards have a Marvell chip equipped with designation:
2025 A0P --> Year 20 Week 25

1) Could that link drop issue be a known issue related to this specific production date of the chip which is assembled on my faulty boards with serial no. 6998XX?

2) Are there any recommendations how to find out the rootcause of my issue?

Best regards
Pages: 1 [2] 3 4 ... 10