Recent Posts

Pages: 1 [2] 3 4 ... 10
11
UltraScale / Re: PL Power Status OFF, cannot connect PL TAP
« Last post by JH on February 03, 2023, 02:24:20 PM »
Depends on the boot mode. If you has JTAG only boot mode and you power on, than it can be a problem on power supply. In case you has a other boot mode and system try to boot without access than it's mostly wrong message from Vivado.
br
John
12
Trenz Electronic FPGA Modules / Re: connect TE0820 JTAG with a JTAG verilog design
« Last post by JH on February 03, 2023, 02:20:32 PM »
Hi,
simple use Vivado and Vitis. Easier than program over JTAG is to generate final boot.bin and boot from SD. Because your bitstream only inbcludes PL part, PS configuration is included into the fsbl (which depends from your xsa export from vivado to Vitis).
We offer Reference Designs and some additional notes to Xilinx(AMD) Documentation:
https://wiki.trenz-electronic.de/display/PD/TE0820+Test+Board
https://wiki.trenz-electronic.de/display/PD/Xilinx+Development+Tools

br
John
13
Trenz Electronic FPGA Modules / connect TE0820 JTAG with a JTAG verilog design
« Last post by aymand on February 03, 2023, 01:53:47 PM »
Hello, I have TE0820-03 on TE0703-04,

I have a design with a JTAG interface, that I want to program to the FPGA, my question is can I send data through the mini-usb interface -which is connected to FTDI2232h- to the programmed FPGA, and any tips on how to do it?

14
Trenz Electronic FPGA Modules / Re: TE0720 VBAT_IN voltage
« Last post by JH on February 02, 2023, 04:42:38 PM »
Hi,
do you have anything else connected to the module over your carrier? The VBAT is also powered by 3.3V, if you are not in battery mode maybe there is some problem on the HW ,which maybe works but which drop down 3.3V power rail from time to time ....
br
John
15
Hi,
this is a relict from older version of the CPLD. We didn't removed it from TE0720 reference design until now. We didn't use drivers for testen and we changed code over the time...
Use simple use I2C get and I2C set function to get access if needed.
br
John
16
I noticed in the TE0720 BSP that the system-user.dtsi has this:

Code: [Select]
/* I2C need I2C1 connected to te0720 system controller ip */
&i2c1 {
 
    iexp@20 {       // GPIO in CPLD
        #gpio-cells = <2>;
        compatible = "ti,pcf8574";
        reg = <0x20>;
        gpio-controller;
    };
 
    iexp@21 {       // GPIO in CPLD
        #gpio-cells = <2>;
        compatible = "ti,pcf8574";
        reg = <0x21>;
        gpio-controller;
    };
 
    rtc@6F {        // Real Time Clock
        compatible = "isl12022";
        reg = <0x6F>;
    };
};

The rtc@6F binding makes sense but I don't understand why the CPLD I2C to GPIO blocks (iexp@20 and iexp@21) are bound to "ti,pcf8574".

If I check /sys/devices/soc0/amba/e0005000.i2c/i2c-1 I see the three devices. But only iexp@21 (and rtc@6F) is bound:
Code: [Select]
root@s6:/sys/devices/soc0/amba/e0005000.i2c/i2c-1# ls -la
total 0
drwxr-xr-x    7 root     root             0 Feb  1 15:34 .
drwxr-xr-x    4 root     root             0 Feb  1 15:34 ..
drwxr-xr-x    3 root     root             0 Feb  1 15:34 1-0020
drwxr-xr-x    5 root     root             0 Feb  1 15:34 1-0021
drwxr-xr-x    4 root     root             0 Feb  1 15:34 1-006f
--w-------    1 root     root          4096 Feb  1 15:51 delete_device
lrwxrwxrwx    1 root     root             0 Feb  1 15:51 device -> ../../e0005000.i2c
drwxr-xr-x    3 root     root             0 Feb  1 15:34 i2c-dev
-r--r--r--    1 root     root          4096 Feb  1 15:51 name
--w-------    1 root     root          4096 Feb  1 15:51 new_device
lrwxrwxrwx    1 root     root             0 Feb  1 15:51 of_node -> ../../../../../firmware/devicetree/base/amba/i2c@e0005000
drwxr-xr-x    2 root     root             0 Feb  1 15:51 power
lrwxrwxrwx    1 root     root             0 Feb  1 15:34 subsystem -> ../../../../../bus/i2c
-rw-r--r--    1 root     root          4096 Feb  1 15:34 uevent
root@s6:/sys/devices/soc0/amba/e0005000.i2c/i2c-1# ls 1-0020 -la
total 0
drwxr-xr-x    3 root     root             0 Feb  1 15:34 .
drwxr-xr-x    7 root     root             0 Feb  1 15:34 ..
-r--r--r--    1 root     root          4096 Feb  1 15:52 modalias
-r--r--r--    1 root     root          4096 Feb  1 15:52 name
lrwxrwxrwx    1 root     root             0 Feb  1 15:52 of_node -> ../../../../../../firmware/devicetree/base/amba/i2c@e0005000/iexp@20
drwxr-xr-x    2 root     root             0 Feb  1 15:52 power
lrwxrwxrwx    1 root     root             0 Feb  1 15:52 subsystem -> ../../../../../../bus/i2c
-rw-r--r--    1 root     root          4096 Feb  1 15:34 uevent
root@s6:/sys/devices/soc0/amba/e0005000.i2c/i2c-1# ls 1-0021 -la
total 0
drwxr-xr-x    5 root     root             0 Feb  1 15:34 .
drwxr-xr-x    7 root     root             0 Feb  1 15:34 ..
lrwxrwxrwx    1 root     root             0 Feb  1 16:04 driver -> ../../../../../../bus/i2c/drivers/pcf857x
drwxr-xr-x    3 root     root             0 Feb  1 15:34 gpio
drwxr-xr-x    3 root     root             0 Feb  1 15:34 gpiochip3
-r--r--r--    1 root     root          4096 Feb  1 16:04 modalias
-r--r--r--    1 root     root          4096 Feb  1 16:04 name
lrwxrwxrwx    1 root     root             0 Feb  1 16:04 of_node -> ../../../../../../firmware/devicetree/base/amba/i2c@e0005000/iexp@21
drwxr-xr-x    2 root     root             0 Feb  1 16:04 power
lrwxrwxrwx    1 root     root             0 Feb  1 16:04 subsystem -> ../../../../../../bus/i2c
-rw-r--r--    1 root     root          4096 Feb  1 15:34 uevent

I also see the probes during the boot:
Code: [Select]
root@s6:~# dmesg | grep 1-00
[    0.860928] pcf857x 1-0021: probed
[    0.863791] rtc-isl12022 1-006f: registered as rtc0
[    1.060969] rtc-isl12022 1-006f: setting system clock to 2023-02-01T22:34:17 UTC (1675290857)

Why doesn't iexp@20 get probed and bound?

Anyone know why these are in the device tree (and possibly how to use them)?

Thanks
18
EDDP-EDPS Support / Re: How to initialize the EDDP by BTN3
« Last post by Jason bourne on February 01, 2023, 02:20:12 AM »
Hi Andrei,

I modified the problem that I said yesterday that it does not work in MODE_MANUAL_TORQUE_FLUX mode, the problem is that we discussed changing the sin-cos table to seven pairs of poles, causing the boot motor to fail to rotate.

best regards
Jason
19
Trenz Electronic FPGA Modules / Re: TE0720 VBAT_IN voltage
« Last post by bigguiness on January 31, 2023, 07:32:12 PM »
BTW, here is an example of the flood of messages I get sometimes.
Code: [Select]
urandom_read: 2 callbacks suppressed
random: udevd: uninitialized urandom read (16 bytes read)
random: udevd: uninitialized urandom read (16 bytes read)
EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
random: dd: uninitialized urandom read (512 bytes read)
Configuring packages on first boot....
 (This may take several minutes. Please do not power off the machine.)
Running postinst /etc/rpm-postinsts/100-sysvinit-inittab...
update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing)
 Removing any system startup links for run-postinsts ...
  /etc/rcS.d/S99run-postinsts
INIT: Entering runlevel: 5
Configuring network interfaces... udhcpc: started, v1.31.0
udhcpc: sending discover
udhcpc: sending discover
macb e000b000.ethernet eth0: link up (1000/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
udhcpc: sending discover
udhcpc: sending select for 10.168.0.97
udhcpc: lease of 10.168.0.97 obtained, lease time 86400
/etc/udhcpc.d/50default: Adding DNS 192.168.0.123
/etc/udhcpc.d/50default: Adding DNS 192.168.0.119
/etc/udhcpc.d/50default: Adding DNS 8.8.8.8
done.
Starting haveged: haveged: listening socket at 3
haveged: haveged starting up


Starting Dropbear SSH server: random: dropbearkey: uninitialized urandom read (32 bytes read)
Generating 2048 bit rsa key, this may take a while...
random: dropbearkey: uninitialized urandom read (32 bytes read)
haveged: haveged: ver: 1.9.5; arch: generic; vend: ; build: (gcc 9.2.0 CTV); collect: 128K

haveged: haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 12/40; sz: 15006/57790

haveged: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B):  last entropy estimate 8.00128

haveged: haveged: fills: 0, generated: 0

random: crng init done
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCm4f/MueYk1rmtwt7axcqFty8ys2V0Dli1xITKrpIGjtvP4fP2vu+tBpEBnF9lzpxCET7L53JK0oam6/zbOqCP6Po25Zt7p6Cvh90AK+efc4I3kyudPNYQVjShDjPnCvvsxpA7mxFpGi4PzHxZi8VVaHviMbZTaXRcuia1JrVd6IIgnnAacWt0Yh0VUAzItuNxRVfBSFywfjHzmt3qPM6mQycsYDJxsL2WI38bGx+F4x5MEAAmzZrC1KNAwyZwSZ1BN9UbtO4FG208SgP3xztpISRkvrlaoq17Zm4lrGry5FYLwH3GkAIZaPxG+yxCncMTpOYGaONLT2tQ9Sr5hiPH root@s6
Fingerprint: sha1!! 60:3d:d2:fe:1b:1b:3e:f7:64:b3:3d:11:21:5e:21:ca:43:52:bb:30
dropbear.
starting Busybox HTTP Daemon: httpd... done.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
rtc-isl12022 1-006f: voltage dropped below 85%, date and time is not reliable.
Starting internet superserver: inetd.
Starting syslogd/klogd: done
Starting tcf-agent: OK

PetaLinux 2020.2 s6 ttyPS0
20
Trenz Electronic FPGA Modules / how to make Petalinux replace /etc/profile
« Last post by bigguiness on January 31, 2023, 07:31:03 PM »
Hello,

I have a modified /etc/profile that I have to copy manually to my board very time I do a 'petalinux-package ...'.

This works, but is annoying.

I have a recipe that copies a number of scripts, etc. to /home/root/bin when I do the 'petalinux-build' but when I tried adding the custom profile file and copying it to /etc/profile I get a build error. Something about a package conflict.

Does anyone know the proper way to replace that file during the build?

Thanks
Pages: 1 [2] 3 4 ... 10