Q&A - Recent Threads

ADDI9036 product status change

mocuZ — Mon, 24 Jun 2024 06:49:45 GMT

Hello,

I recently found that the status of ADDI9036 has changed from "Recommended for New Designs" to "Not Recommended for New Designs". Is this particular chip going to be phased out of production? The project I am responsible for relies solely on this IC and the technologies it brings with itself. Should my team reconsider other options if ADDI9036 it to be stopped from production? And does this mean that I have to throw away more 2 years of development?

I will highly appreciate any advice, additional information, official statements, comments and feedback on the subject.

Kind Regards,

Martin Botsov

ADN8834 VREF

SsangYup — Tue, 10 Oct 2023 05:29:14 GMT

I'm trying to control the TEC of the laser diode through ADN8834 IC.
In the design, ADN8834 was operated using the reference voltage from the outside, but when the reference voltage pin of ADN8834 was left in NC state, the IC did not operate.
Datasheet doesn't mention the reference pin processing when using an external reference, but if not, do I have to connect the Capacitor and process it as GND?
When I connected the Capacitor and processed it as GND, the IC works, so I would appreciate it if you could reply to this.

About reproduction of ad-fmclidar1-ebz

FengxuYang — Thu, 21 Sep 2023 09:05:43 GMT

Dear all,

I know the ad-fmclidar1-ebz platform no longer supports and there are not available in any second distributor, such as Digikey and Mouser. So I am trying to reproduce this platform with the open source hardware files. e.g. .brd file desgined by allegro 17.2. However, I am new to this CAD software so I do not know how to export Gerber files to reproduce the PCB board with the very complex manufacturing parameters.

My question is:

1. Is there anywhere to get access to the Gerber files with parameters already has been set? If so, this will be a great help.

2. If not, is there some guideline on how to export Gerber files step by step?

Very appreciate.

Fengxu

Using the alternative AD9528 clocking without ADF4360-7

mike.looijmans@topicproducts.com — Fri, 11 Nov 2022 10:23:53 GMT

We've a custom design based on the EVM.

In the guides here:
wiki.analog.com/.../hardware_daq

It mentions:

The DAQ board allows for an alternative use of the AD9528 where both its PLL stages are used in addition to the output buffer. This option doesn’t use the separate PLL – ADF4360-7. The block diagram along with the higher power consumption are given in the next figure.

Our hardware engineers have chosen to implement this way of clocking. So now it's up to me to get this to actually work. This complicates the AD9528 settiings considerably, since the PLLs will no longer be in bypass.

Is there a devicetree available that contains the settings that are to be used here?

So far I figured out that:
adi,pll2-m1-frequency = <1000000000>;

lets the driver calculate most of the settings for PLL2. For PLL1 it's not clear to me what needs to be done. Just like the reference design, there's a 25MHz oscillator and a 122.88MHz VCXO

AD-FMCLIDAR1-EBZ with LPC connector on FPGA board

Aballu — Tue, 01 Nov 2022 17:51:46 GMT

Does a FPGA board with only a LPC connector work with the AD-FMCLIDAR1-EBZ? Or does it need a HPC?

Thanks in advance

ADAL6110-16 datasheet?

ScottS — Wed, 21 Sep 2022 17:20:43 GMT

I'm looking for an in-depth datasheet for the ADAL6110-16 multichannel LIDAR front-end IC. More than the 2-page version on the web site.

ADAL6110-16 does not work when powered on

Gavin.du@arrowasia.com — Fri, 02 Sep 2022 09:48:17 GMT

ADAL6110-16 chip does not work when powered on, We have adopted the following methods: 1. Readjust power on sequence, 3.3V and 1.8V soft start time up to 2ms; 2. download the startup code after power on according to the document. After the two methods have been tried, they still fail to start work. If the chip works normally, will the chip send a chip address to MCU through SPI after power on? At present, the chip does not send any information and the chip work current is zero.

We hope to get ADI's technical support as soon as possible. Thank you!

Unable to boot zcu102 with the AD_FMCLIDAR1_EBZ system

inri — Tue, 07 Jun 2022 12:23:36 GMT

Hello everyone,

i want to setup the AD_FMCLIDAR1_EBZ. I follow the instructions described here: https://wiki.analog.com/resources/tools-software/linux-software/embedded_arm_images and i am not able to boot my zcu102 board.

I tryed several times with the newest release (2019_R2) and also with the older version (2019_R1), but i always get the same error:

I will be very thankful for any kind of help.

Thank you in advance!

Unable to Get Data from AD-FMCLIDAR1-EBZ with ZCU102

AlexJT — Wed, 16 Mar 2022 15:56:22 GMT

Hello,

I am posting this inquiry in regards to the Analog Devices AD-FMCLIDAR1-EBZ Lidar prototyping platform. We have been in the process of following the instructions on the Analog Devices wiki in order to run the Lidar prototype via a Xilinx Zynq UltraScale+ MPSoC ZCU102. We have successfully booted up the Linux image supplied to us via the link here, and we are able to access the Linux system over serial terminal, as well as through an attached keyboard/mouse and computer monitor. When we set up the SD card, we made sure to copy the necessary files to the boot of the SD card. These files included zynqmp-zcu102-rev10-fmclidar1/BOOT.BIN, zynqmp-zcu102-rev10-fmclidar1/system.dtb, and zynqmp-common/Image. IIO_Oscilloscope is installed, and we have had no trouble launching it.

However, we are unable to see any of the ADC outputs from the AD-FMCLIDAR1-EBZ. We can confirm their absence by running the iio_info | grep device command, which results in the following list of devices:

IIO context has 5 devices:

iio:device0: ams

1 device-specific attributes found:

No trigger on this device

iio:device1: pll

No trigger on this device

iio:device2: ad5627

No trigger on this device

iio:device3: ad7091 (buffer capable)

1 device-specific attributes found:

2 device-specific attributes found:

No trigger on this device

Furthermore, when booting up IIO_Oscilloscope, the only windows available are the main scope interface, as well as the DMM and Debug windows. The wiki seems to suggest that we should have more options relating to the Lidar available, but these are nowhere to be found.

We also made sure to build the HDL environment using the repository found here, and the instructions found here. We had no trouble running synthesis & implementation, and we were able to generate the bitstream and program the device on the zcu102. However, doing this did not help, and we remained unable to see the ADC channels on the Lidar board. After this, we ran the commands sudo adi_update_tools.sh and sudo adi_update_boot.sh, which ran without issue. This failed to fix the behavior we were seeing. We also attempted a soft reboot, which fixed nothing. In order to attempt debugging, we probed all of the test points on the DAC board, and we were able to verify that the ADP5054 is functional, and that it is supplying two 1.3 V outputs, one 2.4 V output, and one 3.0 V output. Still, we get the same output for the iio_info. We also probed the lines for DUT_CLK+, DUT_CLK-, D_SYSREF_P, and D_SYSREF_N, and all of them sit at 750 mV without any sign of clocking.

Can you please inform us of what actions we need to take to get this board operational? We want to get to the point where we are able to capture distance readings with the Lidar sensor, but we cannot do that until we resolve this.

Thank You

Additional Note:

We noticed that the DAQ board said Rev C on it, but the link (https://wiki.analog.com/_media/resources/eval/user-guides/ad-fmclidar1-ebz/revb_daq.zip) to download the BOM, schematics and layout are Rev B (it's in the link filename at the end, which is why I pasted it in). We also noticed, in this link, that there were multiple changes in the io constraints file from Rev A to Rev B, so maybe there should be some from Rev B to C too?

Lidar for AGV/ laser measuring tool

jiamin — Thu, 21 Oct 2021 01:40:31 GMT

Hi,

I'm looking for ToF or Lidar solution for AGV/ laser measuring tool.

Range: 4meters

Fov/ Beam convergent: 1° (current Garmin Lite v4 is 4° is too big when it arrives 3.5m it is already about 30cm, want to pin point)

Update Rate: 5ms /200Hz (the faster the better)

Is ADI Lidar capable of achieving this requirement? is there any solution without using FPGA? Could we use MCU instead?

LiDAR Customer Prototyping Platform release schedule (AD-FMCLIDAR1-EBZ)

Nat.Wong — Tue, 01 Jun 2021 07:09:00 GMT

Hi Sirs

Do you provide the AD-FMCLIDAR1-EBZ release schedule?

the status is pre-release.

Could you help us to check the release schedule?

I want to but the EVM to test.

Thank you very much.

BRS

Nat

AD-FMCLIDAR1-EBZ+ZC706's boot log

JaksonTee — Mon, 15 Mar 2021 04:31:54 GMT

Hi, I updated the SD boot image “23 February 2021 release candidate (2019_R2)” through Etcher.

But Etcher's check result at the end of write stage was fail.and the 32GB sd card's capacity was changed to less than 1GB.

The boot log was followed. Although there were some fail,but the linux Os started watching from the monitor.

Please confirm does it work fine?

Thanks.


U-Boot 2014.07-dirty (Nov 20 2014 - 17:07:55)

Board:	Xilinx Zynq
I2C:   ready
DRAM:  ECC disabled 1 GiB
MMC:   zynq_sdhci: 0
SF: Detected S25FL128S_64K with page size 512 Bytes, erase size 128 KiB, total 32 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   Gem.e000b000
Hit any key to stop autoboot:  3  2  1  0 
Device: zynq_sdhci
Manufacturer ID: ff
OEM: 0
Name: SDU1  
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.4 GiB
Bus Width: 4-bit
reading uEnv.txt
407 bytes read in 27 ms (14.6 KiB/s)
Loaded environment from uEnv.txt
Importing environment from SD ...
Running uenvcmd ...
Copying Linux from SD to RAM...
reading uImage
6484280 bytes read in 580 ms (10.7 MiB/s)
reading devicetree.dtb
18102 bytes read in 42 ms (420.9 KiB/s)
reading uramdisk.image.gz
** Unable to read file uramdisk.image.gz **
## Booting kernel from Legacy Image at 03000000 ...
   Image Name:   Linux-4.19.0-ga6ef26d
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6484216 Bytes = 6.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 02a00000
   Booting using the fdt blob at 0x2a00000
   Loading Kernel Image ... OK
   Loading Device Tree to 1fff8000, end 1ffff6b5 ... OK

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.19.0-ga6ef26d (jenkins@romlxbuild1.adlk.analog.com) (gcc version 8.2.0 (GCC)) #1104 SMP PREEMPT Fri Feb 19 15:59:18 GMT 2021
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: Xilinx Zynq ZC706
OF: fdt: earlycon: stdout-path /amba@0/uart@E0001000 not found
Memory policy: Data cache writealloc
cma: Reserved 128 MiB at 0x38000000
random: get_random_bytes called from start_kernel+0xa0/0x404 with crng_init=0
percpu: Embedded 16 pages/cpu @(ptrval) s33548 r8192 d23796 u65536
Built 1 zonelists, mobility grouping on.  Total pages: 260608
Kernel command line: console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlycon rootfstype=ext4 rootwait clk_ignore_unused cpuidle.off=1
Booting kernel: `1 invalid for parameter `cpuidle.off'
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 888444K/1048576K available (9216K kernel code, 760K rwdata, 7012K rodata, 1024K init, 163K bss, 29060K reserved, 131072K cma-reserved, 131072K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0x(ptrval) - 0x(ptrval)   (10208 kB)
      .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
      .data : 0x(ptrval) - 0x(ptrval)   ( 761 kB)
       .bss : 0x(ptrval) - 0x(ptrval)   ( 164 kB)
rcu: Preemptible hierarchical RCU implementation.
rcu: 	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
	Tasks RCU enabled.
rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
efuse mapped to (ptrval)
slcr mapped to (ptrval)
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at (ptrval)
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
timer #0 at (ptrval), irq=17
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
CPU: Testing write buffer coherency: ok
CPU0: Spectre v2: using BPIALL workaround
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100060
rcu: Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
CPU1: Spectre v2: using BPIALL workaround
smp: Brought up 1 node, 2 CPUs
SMP: Total of 2 processors activated (1333.33 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 512 (order: 3, 32768 bytes)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ocmc: ZYNQ OCM pool: 256 KiB @ 0x(ptrval)
zynq-pinctrl 700.pinctrl: zynq pinctrl initialized
e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 26, base_baud = 3125000) is a xuartps
console [ttyPS0] enabled
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
videodev: Linux video capture interface: v2.00
jesd204: found 0 devices and 0 topologies
FPGA manager framework
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
hw perfevents: no interrupt-affinity property for /pmu@f8891000, guessing.
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
workingset: timestamp_bits=30 max_order=18 bucket_order=0
bounce: pool size: 64 pages
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
io scheduler mq-deadline registered
io scheduler kyber registered
dma-pl330 f8003000.dmac: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.dmac: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
brd: module loaded
loop: module loaded
Registered mathworks_ip class
xilinx_spi 7c500000.axi_quad_spi: no CS gpios available
xilinx_spi 7c600000.axi_quad_spi: no CS gpios available
m25p80 spi4.0: found s25fl128s, expected n25q128a11
m25p80 spi4.0: s25fl128s (32768 Kbytes)
5 fixed-partitions partitions found on MTD device spi4.0
Creating 5 MTD partitions on "spi4.0":
0x000000000000-0x000000500000 : "boot"
0x000000500000-0x000000520000 : "bootenv"
0x000000520000-0x000000540000 : "config"
0x000000540000-0x000000fc0000 : "image"
0x000000fc0000-0x000002000000 : "spare"
MACsec IEEE 802.1AE
libphy: Fixed MDIO Bus: probed
tun: Universal TUN/TAP device driver, 1.6
libphy: MACB_mii_bus: probed
Marvell 88E1116R e000b000.ethernet-ffffffff:07: attached PHY driver [Marvell 88E1116R] (mii_bus:phy_addr=e000b000.ethernet-ffffffff:07, irq=POLL)
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 30 (00:0a:35:00:01:22)
usbcore: registered new interface driver asix
usbcore: registered new interface driver ax88179_178a
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
usbcore: registered new interface driver uas
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver upd78f0730
usbserial: USB Serial support registered for upd78f0730
chipidea-usb2 e0002000.usb: e0002000.usb supply vbus not found, using dummy regulator
chipidea-usb2 e0002000.usb: Linked as a consumer to regulator.0
ULPI transceiver vendor/product ID 0x0424/0x0007
Found SMSC USB3320 ULPI transceiver.
ULPI integrity check: passed.
ci_hdrc ci_hdrc.0: EHCI Host Controller
ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1
ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.19.0-ga6ef26d ehci_hcd
usb usb1: SerialNumber: ci_hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
i2c /dev entries driver
cdns-i2c e0005000.i2c: 400 kHz mmio e0005000 irq 23
si570 2-005d: registered, current frequency 156250000 Hz
i2c i2c-1: Added multiplexed i2c bus 2
adv7511 3-0039: 3-0039 supply avdd not found, using dummy regulator
adv7511 3-0039: Linked as a consumer to regulator.0
adv7511 3-0039: 3-0039 supply dvdd not found, using dummy regulator
adv7511 3-0039: 3-0039 supply pvdd not found, using dummy regulator
adv7511 3-0039: 3-0039 supply bgvdd not found, using dummy regulator
adv7511 3-0039: 3-0039 supply dvdd-3v not found, using dummy regulator
i2c i2c-1: Added multiplexed i2c bus 3
at24 4-0054: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
i2c i2c-1: Added multiplexed i2c bus 4
pca953x 5-0021: 5-0021 supply vcc not found, using dummy regulator
pca953x 5-0021: Linked as a consumer to regulator.0
i2c i2c-1: Added multiplexed i2c bus 5
rtc-pcf8563 6-0051: low voltage detected, date/time is not reliable.
rtc-pcf8563 6-0051: rtc core: registered rtc-pcf8563 as rtc0
i2c i2c-1: Added multiplexed i2c bus 6
i2c i2c-1: Added multiplexed i2c bus 7
i2c i2c-1: Added multiplexed i2c bus 8
i2c i2c-1: Added multiplexed i2c bus 9
pca954x 1-0074: registered 8 multiplexed busses for I2C switch pca9548
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
gspca_main: v2.14.0 registered
cdns-wdt f8005000.watchdog: Xilinx Watchdog Timer with timeout 10s
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.mmc [e0100000.mmc] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ad7476 spi3.0: Linked as a consumer to regulator.2
ad9680 spi0.0: Unrecognized CHIP_ID 0xFF
mmc0: new high speed SDHC card at address 59b4
mmcblk0: mmc0:59b4 SDU1  29.4 GiB 
ltc2471 0-0014: Cannot read from device.
ltc2471: probe of 0-0014 failed with error -11
 mmcblk0: p1 p2 p3
ad5064 0-000c: Linked as a consumer to regulator.3
axi_sysid 45000000.axi-sysid-0: [ad_fmclidar1_ebz] on [zc706] git <7c86b9f84f75d6eaad0ef29a31e74b6f6f37c447> clean [2021-02-15 21:50:43] UTC
fpga_manager fpga0: Xilinx Zynq FPGA Manager registered
usbcore: registered new interface driver snd-usb-audio
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 36
Registering SWP/SWPB emulation handler
[drm] Cannot find any crtc or sizes
[drm] Initialized axi_hdmi_drm 1.0.0 20120930 for 70e00000.axi_hdmi on minor 0
ad9528 spi1.0: spi1.0 supply vcc not found, using dummy regulator
ad9528 spi1.0: Linked as a consumer to regulator.0
iio iio:device4: SPI Read Verify failed (0xFFFFFF)
ad9528 spi1.0: Dropping the link to regulator.0
ad9528: probe of spi1.0 failed with error -5
asoc-simple-card adv7511_hdmi_snd: spdif-hifi <-> 75c00000.axi-spdif-tx mapping ok
input: gpio_keys as /devices/soc0/gpio_keys/input/input0
rtc-pcf8563 6-0051: low voltage detected, date/time is not reliable.
rtc-pcf8563 6-0051: hctosys: unable to read the hardware clock
clk: Not disabling unused clocks
ALSA device list:
  #0: HDMI monitor
random: fast init done
EXT4-fs (mmcblk0p2): recovery complete
EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:2.
devtmpfs: mounted
Freeing unused kernel memory: 1024K
Run /sbin/init as init process
systemd[1]: System time before build time, advancing clock.
systemd[1]: Failed to lookup module alias 'autofs4': Function not implemented
[drm] Cannot find any crtc or sizes
systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
systemd[1]: Detected architecture arm.

Welcome to [1mKuiper GNU/Linux 10 (buster)[0m!

systemd[1]: Set hostname to <analog>.
systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
systemd[1]: /etc/systemd/system/tof-server.service:1: Assignment outside of section. Ignoring.
systemd[1]: /etc/systemd/system/tof-server.service:2: Assignment outside of section. Ignoring.
random: systemd: uninitialized urandom read (16 bytes read)
random: systemd: uninitialized urandom read (16 bytes read)
systemd[1]: Created slice system-serial\x2dgetty.slice.
[[0;32m  OK  [0m] Created slice [0;1;39msystem-serial\x2dgetty.slice[0m.
random: systemd: uninitialized urandom read (16 bytes read)
systemd[1]: Listening on udev Control Socket.
[[0;32m  OK  [0m] Listening on [0;1;39mudev Control Socket[0m.
systemd[1]: Listening on fsck to fsckd communication Socket.
[[0;32m  OK  [0m] Listening on [0;1;39mfsck to fsckd communication Socket[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mudev Kernel Socket[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mSwap[0m.
[[0;32m  OK  [0m] Started [0;1;39mForward Password R鈥ests to Wall Directory Watch[0m.
[[0;32m  OK  [0m] Listening on [0;1;39minitctl Compatibility Named Pipe[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mJournal Socket[0m.
         Starting [0;1;39mLoad Kernel Modules[0m...
         Starting [0;1;39mudev Coldplug all Devices[0m...
         Starting [0;1;39mRestore / save the current clock[0m...
         Mounting [0;1;39mRPC Pipe File System[0m...
[[0;32m  OK  [0m] Listening on [0;1;39mJournal Socket (/dev/log)[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mSyslog Socket[0m.
[[0;32m  OK  [0m] Created slice [0;1;39msystem-systemd\x2dfsck.slice[0m.
[[0;32m  OK  [0m] Created slice [0;1;39msystem-getty.slice[0m.
         Starting [0;1;39mJournal Service[0m...
         Starting [0;1;39mSet the console keyboard layout[0m...
         Mounting [0;1;39mKernel Debug File System[0m...
[[0;32m  OK  [0m] Created slice [0;1;39mUser and Session Slice[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mSlices[0m.
[[0;1;31mFAILED[0m] Failed to start [0;1;39mLoad Kernel Modules[0m.
See 'systemctl status systemd-modules-load.service' for details.
[[0;32m  OK  [0m] Started [0;1;39mRestore / save the current clock[0m.
[[0;32m  OK  [0m] Started [0;1;39mJournal Service[0m.
[[0;1;31mFAILED[0m] Failed to mount [0;1;39mRPC Pipe File System[0m.
See 'systemctl status run-rpc_pipefs.mount' for details.
[[0;1;33mDEPEND[0m] Dependency failed for [0;1;39mRPC 鈥urity service for NFS server[0m.
[[0;1;33mDEPEND[0m] Dependency failed for [0;1;39mRPC 鈥ce for NFS client and server[0m.
[[0;32m  OK  [0m] Mounted [0;1;39mKernel Debug File System[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mNFS client services[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mRemote File Systems (Pre)[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mRemote File Systems[0m.
         Starting [0;1;39mRemount Root and Kernel File Systems[0m...
         Starting [0;1;39mApply Kernel Variables[0m...
         Mounting [0;1;39mKernel Configuration File System[0m...
[[0;32m  OK  [0m] Started [0;1;39mudev Coldplug all Devices[0m.
[[0;32m  OK  [0m] Started [0;1;39mSet the console keyboard layout[0m.
[[0;32m  OK  [0m] Started [0;1;39mApply Kernel Variables[0m.
[[0;32m  OK  [0m] Mounted [0;1;39mKernel Configuration File System[0m.
         Starting [0;1;39mHelper to synchronize boot up for ifupdown[0m...
[[0;32m  OK  [0m] Started [0;1;39mHelper to synchronize boot up for ifupdown[0m.
[[0;32m  OK  [0m] Started [0;1;39mRemount Root and Kernel File Systems[0m.
         Starting [0;1;39mCreate System Users[0m...
         Starting [0;1;39mLoad/Save Random Seed[0m...
         Starting [0;1;39mFlush Journal to Persistent Storage[0m...
[[0;32m  OK  [0m] Started [0;1;39mCreate System Users[0m.
[[0;32m  OK  [0m] Started [0;1;39mLoad/Save Random Seed[0m.
         Starting [0;1;39mCreate Static Device Nodes in /dev[0m...
[[0;32m  OK  [0m] Started [0;1;39mFlush Journal to Persistent Storage[0m.
[[0;32m  OK  [0m] Started [0;1;39mCreate Static Device Nodes in /dev[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mLocal File Systems (Pre)[0m.
         Starting [0;1;39mudev Kernel Device Manager[0m...
[[0;32m  OK  [0m] Started [0;1;39mudev Kernel Device Manager[0m.
         Starting [0;1;39mShow Plymouth Boot Screen[0m...
[[0;32m  OK  [0m] Started [0;1;39mShow Plymouth Boot Screen[0m.
[[0;32m  OK  [0m] Started [0;1;39mForward Password R鈥 to Plymouth Directory Watch[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mLocal Encrypted Volumes[0m.
[[0m[0;31m*     [0m] (1 of 4) A start job is running for /dev/serial1 (7s / 1min 30s)
M
[K[[0;1;31m*[0m[0;31m*    [0m] (1 of 4) A start job is running for /dev/serial1 (8s / 1min 30s)
M
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (1 of 4) A start job is running for /dev/serial1 (8s / 1min 30s)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (2 of 4) A start job is running for /dev/ttyS0 (9s / 1min 30s)
M
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (2 of 4) A start job is running for /dev/ttyS0 (9s / 1min 30s)
M
[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] (2 of 4) A start job is running for /dev/ttyS0 (10s / 1min 30s)
M
[K[    [0;31m*[0;1;31m*[0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (10s / 1min 30s)
M
[K[     [0;31m*[0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (11s / 1min 30s)
M
[K[    [0;31m*[0;1;31m*[0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (11s / 1min 30s)
M
[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] (4 of 4) A start job is running for /dev/ttyPS0 (12s / 1min 30s)
M
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (4 of 4) A start job is running for /dev/ttyPS0 (12s / 1min 30s)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (4 of 4) A start job is running for /dev/ttyPS0 (13s / 1min 30s)
M
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (1 of 4) A start job is running for /dev/serial1 (13s / 1min 30s)
M
[K[[0;1;31m*[0m[0;31m*    [0m] (1 of 4) A start job is running for /dev/serial1 (14s / 1min 30s)
M
[K[[0m[0;31m*     [0m] (1 of 4) A start job is running for /dev/serial1 (14s / 1min 30s)
M
[K[[0;1;31m*[0m[0;31m*    [0m] (2 of 4) A start job is running for /dev/ttyS0 (15s / 1min 30s)
M
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (2 of 4) A start job is running for /dev/ttyS0 (15s / 1min 30s)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (2 of 4) A start job is running for /dev/ttyS0 (16s / 1min 30s)
M
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (16s / 1min 30s)
M
[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (17s / 1min 30s)
M
[K[    [0;31m*[0;1;31m*[0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (17s / 1min 30s)
M
[K[     [0;31m*[0m] (4 of 4) A start job is running for /dev/ttyPS0 (18s / 1min 30s)
M
[K[    [0;31m*[0;1;31m*[0m] (4 of 4) A start job is running for /dev/ttyPS0 (18s / 1min 30s)
M
[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] (4 of 4) A start job is running for /dev/ttyPS0 (19s / 1min 30s)
M
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (1 of 4) A start job is running for /dev/serial1 (19s / 1min 30s)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (1 of 4) A start job is running for /dev/serial1 (20s / 1min 30s)
M
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (1 of 4) A start job is running for /dev/serial1 (20s / 1min 30s)
M
[K[[0;1;31m*[0m[0;31m*    [0m] (2 of 4) A start job is running for /dev/ttyS0 (21s / 1min 30s)
M
[K[[0m[0;31m*     [0m] (2 of 4) A start job is running for /dev/ttyS0 (21s / 1min 30s)
M
[K[[0;1;31m*[0m[0;31m*    [0m] (2 of 4) A start job is running for /dev/ttyS0 (22s / 1min 30s)
M
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (22s / 1min 30s)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (23s / 1min 30s)
M
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (23s / 1min 30s)
M
[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] (4 of 4) A start job is running for /dev/ttyPS0 (24s / 1min 30s)
M
[K[    [0;31m*[0;1;31m*[0m] (4 of 4) A start job is running for /dev/ttyPS0 (24s / 1min 30s)
M
[K[     [0;31m*[0m] (4 of 4) A start job is running for /dev/ttyPS0 (25s / 1min 30s)
M
[K[    [0;31m*[0;1;31m*[0m] (1 of 4) A start job is running for /dev/serial1 (25s / 1min 30s)
M
[K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] (1 of 4) A start job is running for /dev/serial1 (26s / 1min 30s)
M
[K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] (1 of 4) A start job is running for /dev/serial1 (26s / 1min 30s)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (2 of 4) A start job is running for /dev/ttyS0 (27s / 1min 30s)
M
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (2 of 4) A start job is running for /dev/ttyS0 (27s / 1min 30s)
M
[K[[0;1;31m*[0m[0;31m*    [0m] (2 of 4) A start job is running for /dev/ttyS0 (28s / 1min 30s)
M
[K[[0m[0;31m*     [0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (28s / 1min 30s)
M
[K[[0;1;31m*[0m[0;31m*    [0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (29s / 1min 30s)
M
[K[[0;31m*[0;1;31m*[0m[0;31m*   [0m] (3 of 4) A start job is running for鈥uuid/18f1f9d5-01 (29s / 1min 30s)
M
[K[ [0;31m*[0;1;31m*[0m[0;31m*  [0m] (4 of 4) A start job is running for /dev/ttyPS0 (30s / 1min 30s)
M
[K         Starting [0;1;39mLoad Kernel Modules[0m...
[K[[0;32m  OK  [0m] Found device [0;1;39m/dev/ttyPS0[0m.
[[0;1;31mFAILED[0m] Failed to start [0;1;39mLoad Kernel Modules[0m.
See 'systemctl status systemd-modules-load.service' for details.
[[0;32m  OK  [0m] Found device [0;1;39m/dev/disk/by-partuuid/18f1f9d5-01[0m.
         Starting [0;1;39mFile System Check鈥sk/by-partuuid/18f1f9d5-01[0m...
[[0;32m  OK  [0m] Started [0;1;39mFile System Check Daemon to report status[0m.
[[0;32m  OK  [0m] Started [0;1;39mFile System Check 鈥disk/by-partuuid/18f1f9d5-01[0m.
         Mounting [0;1;39m/boot[0m...
[[0;32m  OK  [0m] Mounted [0;1;39m/boot[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mLocal File Systems[0m.
         Starting [0;1;39mTell Plymouth To Write Out Runtime Data[0m...
         Starting [0;1;39mPreprocess NFS configuration[0m...
         Starting [0;1;39mRaise network interfaces[0m...
         Starting [0;1;39mCreate Volatile Files and Directories[0m...
         Starting [0;1;39mSet console font and keymap[0m...
[[0;32m  OK  [0m] Started [0;1;39mTell Plymouth To Write Out Runtime Data[0m.
[[0;32m  OK  [0m] Started [0;1;39mPreprocess NFS configuration[0m.
[[0;32m  OK  [0m] Started [0;1;39mSet console font and keymap[0m.
[[0;32m  OK  [0m] Started [0;1;39mCreate Volatile Files and Directories[0m.
         Starting [0;1;39mNetwork Time Synchronization[0m...
         Starting [0;1;39mUpdate UTMP about System Boot/Shutdown[0m...
[[0;32m  OK  [0m] Started [0;1;39mNetwork Time Synchronization[0m.
[[0;32m  OK  [0m] Started [0;1;39mUpdate UTMP about System Boot/Shutdown[0m.
[[0;32m  OK  [0m] Started [0;1;39mRaise network interfaces[0m.
         Starting [0;1;39mTell Plymouth To Write Out Runtime Data[0m...
         Starting [0;1;39mLoad Kernel Modules[0m...
[[0;32m  OK  [0m] Reached target [0;1;39mSystem Time Synchronized[0m.
[[0;32m  OK  [0m] Started [0;1;39mTell Plymouth To Write Out Runtime Data[0m.
[[0;1;31mFAILED[0m] Failed to start [0;1;39mLoad Kernel Modules[0m.
See 'systemctl status systemd-modules-load.service' for details.
[[0;32m  OK  [0m] Reached target [0;1;39mSystem Initialization[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mCUPS Scheduler[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mD-Bus System Message Bus Socket[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily Cleanup of Temporary Directories[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mAvahi mDNS/DNS-SD Stack Activation Socket[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily apt download activities[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily apt upgrade and clean activities[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mtriggerhappy.socket[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily rotation of log files[0m.
[[0;32m  OK  [0m] Started [0;1;39mDaily man-db regeneration[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mTimers[0m.
[[0;32m  OK  [0m] Listening on [0;1;39mGPS (Global P鈥oning System) Daemon Sockets[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mSockets[0m.
[[0;32m  OK  [0m] Started [0;1;39mCUPS Scheduler[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mPaths[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mBasic System[0m.
         Starting [0;1;39mCheck for Raspberry Pi EEPROM updates[0m...
         Starting [0;1;39mrng-tools.service[0m...
[[0;32m  OK  [0m] Started [0;1;39mRegular background program processing daemon[0m.
[[0;32m  OK  [0m] Started [0;1;39mtof-server.service[0m.
         Starting [0;1;39mLSB: Switch to on鈥less shift key is pressed)[0m...
         Starting [0;1;39mModem Manager[0m...
         Starting [0;1;39mDisk Manager[0m...
[[0;32m  OK  [0m] Started [0;1;39mD-Bus System Message Bus[0m.
         Starting [0;1;39mLogin Service[0m...
         Starting [0;1;39mSystem Logging Service[0m...
         Starting [0;1;39mdhcpcd on all interfaces[0m...
         Starting [0;1;39mAvahi mDNS/DNS-SD Stack[0m...
[[0;32m  OK  [0m] Started [0;1;39mManage Sound Card State (restore and store)[0m.
         Starting [0;1;39mSave/Restore Sound Card State[0m...
         Starting [0;1;39mtriggerhappy global hotkey daemon[0m...
         Starting [0;1;39mWPA supplicant[0m...
[[0;32m  OK  [0m] Started [0;1;39mCUPS Scheduler[0m.
         Starting [0;1;39mdphys-swapfile - 鈥nt, and delete a swap file[0m...
[[0;32m  OK  [0m] Started [0;1;39mtriggerhappy global hotkey daemon[0m.
[[0;32m  OK  [0m] Started [0;1;39mSystem Logging Service[0m.
[[0;32m  OK  [0m] Started [0;1;39mCheck for Raspberry Pi EEPROM updates[0m.
[[0;1;31mFAILED[0m] Failed to start [0;1;39mrng-tools.service[0m.
See 'systemctl status rng-tools.service' for details.
[[0;32m  OK  [0m] Started [0;1;39mSave/Restore Sound Card State[0m.
[[0;32m  OK  [0m] Started [0;1;39mdhcpcd on all interfaces[0m.
[[0;32m  OK  [0m] Started [0;1;39mLogin Service[0m.
         Starting [0;1;39mAuthorization Manager[0m...
[[0;32m  OK  [0m] Reached target [0;1;39mSound Card[0m.
[[0;32m  OK  [0m] Started [0;1;39mAvahi mDNS/DNS-SD Stack[0m.
[[0;32m  OK  [0m] Started [0;1;39mWPA supplicant[0m.
[[0;32m  OK  [0m] Reached target [0;1;39mNetwork[0m.
[[0;32m  OK  [0m] Started [0;1;39mIIO Daemon[0m.
         Starting [0;1;39m/etc/rc.local Compatibility[0m...
         Starting [0;1;39mOpenBSD Secure Shell server[0m...
         Starting [0;1;39mHTTP based time synchronization tool[0m...
         Starting [0;1;39mPermit User Sessions[0m...
[[0;32m  OK  [0m] Started [0;1;39mMake remote CUPS printers available locally[0m.
[[0;32m  OK  [0m] Started [0;1;39m/etc/rc.local Compatibility[0m.
[[0;32m  OK  [0m] Started [0;1;39mHTTP based time synchronization tool[0m.
[[0;32m  OK  [0m] Started [0;1;39mdphys-swapfile - s鈥ount, and delete a swap file[0m.
[[0;32m  OK  [0m] Started [0;1;39mPermit User Sessions[0m.
[[0;32m  OK  [0m] Started [0;1;39mLSB: Switch to ond鈥unless shift key is pressed)[0m.
         Starting [0;1;39mHold until boot process finishes up[0m...
         Starting [0;1;39mLight Display Manager[0m...
[[0;32m  OK  [0m] Started [0;1;39mAuthorization Manager[0m.
[[0;32m  OK  [0m] Started [0;1;39mOpenBSD Secure Shell server[0m.
[[0;32m  OK  [0m] Started [0;1;39mModem Manager[0m.

Raspbian GNU/Linux 10 analog ttyPS0

analog login: root (automatic login)

Last login: Wed Feb 24 01:09:50 GMT 2021 on ttyPS0
Linux analog 4.19.0-ga6ef26d #1104 SMP PREEMPT Fri Feb 19 15:59:18 GMT 2021 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@analog:~#

how to check the configuration mode of ad9094 on ad-fmclidar1-ebz

JaksonTee — Tue, 09 Mar 2021 09:19:10 GMT

In which file i could find the register configured of ad9094 that the default SD card that comes with the kit?

Thanks.

LD's FAC angle

JaksonTee — Fri, 05 Mar 2021 02:26:15 GMT

"The detection range can be significantly improved by adding fast-axis-collimator (FAC) lenses in front of the four lasers to narrow the laser beam vertical divergence from 15° of 1°."

Is there something wrong about the angle above described.

From the datasheet of splll 90-3,the fast-axis divergence angle is 30° and from picture of lens placed ,the lens was used to collimate the fast-axis.

Cannot get data from AD-FMCLIDAR1-EBZ with zcu102

ac_um — Fri, 20 Nov 2020 17:11:00 GMT

Hi, my name is André Campos and I'm currently starting my Master's project in LiDAR sensors for automotive. Since the main task of the project is understanding and accelerate intrinsic LiDAR procedures, the Analog AD_FMCLIDAR1_EBZ kit alongside a Xilinx ZCU102 (HPC-FMC enabled) is naturally the chosen setup for developing my work.

In order to test the AD_FMCLIDAR1_EBZ kit, I started by trying to run the examples provided by https://wiki.analog.com/resources/eval/user-guides/ad-fmclidar1-ebz/system_evaluation but when I run ADI IIO Oscilloscope didn't load the LIDAR plugin and on the plot window the axi_ad9094-hpc didn't appear as well. Running jesd_scan_eye results in a window without any information with some errors in the terminal (output at the end).

Until now, I tried different things in order to put a functional image into the ZCU102.

I started by using the image that comes in the kit's sd card, however, I notice that the directory zynqmp-zcu102-rev10-fmclidar1 was missing. So, I used zynqmp-zcu102-rev10-ad9361-fmcomms2-3 to copy the boot.bin and the system.dtb to the BOOT partition.

Since the HDMI monitor was not showing anything, I used the USB terminal and ssh to communicate with the board.

Once the board booted, I followed this https://wiki.analog.com/resources/tools-software/linux-software/embedded_arm_images to update the userspace tools by running adi_update_tools.sh and adi_update_boot.sh to get the missing BOOT files.

After the BOOT files were changed to the ones inside zynqmp-zcu102-rev10-fmclidar1 directory, I connected AD_FCMLIDAR1_EBZ to the ZCU102 ( https://www.xilinx.com/products/boards-and-kits/ek-u1-zcu102-g.html ) using the FMC hpc0, turned the board ON, and run OSC and jesd_scan_eye using an ssh terminal with x11 forwarding.

Since the output (Logs at the end) was different from the one that is described on https://wiki.analog.com/resources/eval/user-guides/ad-fmclidar1-ebz/system_evaluation , I tested the following:

Downloading and using different images following this: https://wiki.analog.com/resources/tools-software/linux-software/zynq_images/linux_hosts .
Generate my self the bitstream using this https://github.com/analogdevicesinc/hdl/tree/vivado_19_2_upgrade/projects/ad_fmclidar1_ebz and then generate the boot.bin using the files inside BOOT/zynqmp-zcu102-rev10-fmclidar1/bootgen_sysfiles.tgz.

However, the results were the same.

Is there anything that I did wrong? Or did I missed something? It is possible to provide more information about the board's digital connectors that compose the kit? And also about the FPGA hardware IPs?

Thanks in advance.

ez.analog.com/.../IO_5F00_Oscilloscope_5F00_output.txt ez.analog.com/.../boot_5F00_output.txt ez.analog.com/.../jesd_5F00_scan_5F00_eye-_5F00_output.txt

AD-FMCLIDAR1-EBZ:About the princple of the LT6016 Feedback circuit

YYF — Mon, 28 Sep 2020 09:35:44 GMT

Hi,I've been studying the AD-FMCLIDAR1-EBZ AFE Board recently.I don't understand the function and the principle of the LT6016 circuit.

If the light intensity is low enough, for example, the apd current will be less than 100nA,and then the TIA output will be less than 7.5mV. Under this condition，the tia output measured value is 1V.

Does this phenomenon means that the 1V reference voltage bypasses all light with low intensity？Does it means only when the Iapd*Rf>1V, the effective voltage value can be sampled by the ADC？

I wonder how the LT6016 circiut works?

Thank you for your answers~

ad-fmclidar1-ebz

Ray_yilei — Fri, 25 Sep 2020 02:27:09 GMT

Hi! I encountered some problems when using the ad-fmclidar1-ebz evaluation kit. When configuring the 0x0550 register of ad9094 to work in test mode and output ramp or 1/0 word toggle signals, the signals received by FPGA are correct. But when ad9094 is working in normal mode to collect the signals of input channels, the signals received by FPGA always seem to be noise. FPGA can not acquire the laser echo signals. There should be no problem with the driver and the TIA output signal is also normal. I used the ZC706. I refered to the driver for ad9094 on github(github.com/.../masteand wrote the software myself. I used the JESD204B ip core in Vivado and the ILA probes connected to the ip core's outputs. I can see the echoed signals on IIO Oscilloscope, but cannot in my own software. So I think there is something wrong in my software, but I don't know what it is. Look forward for your support! Thanks!

AD9094 configuration file for AD-FMCLIDAR1-EBZ

ADIApproved — Thu, 10 Sep 2020 09:32:13 GMT

Hi Guys,

Would you please help to share the AD9094 configuration source file(like register file) of AD-FMCLIDAR1-EBZ? I need it to debug AD9094 mannually. Thanks.

Want to visualize multiple return data from Laser

YouMeWTatsu — Thu, 03 Sep 2020 07:54:48 GMT

I think AD-FMCLIDAR1-EBZ can get multiple return data from laser.
Is it possible to get and visualize multiple return data (1st, 2nd, 3rd) with Lidar.py or other Python apps?

https://github.com/analogdevicesinc/pyadi-iio/blob/master/examples/lidar.py

Thank you.

Can FISBA lenses measure 60 m?

YouMeWTatsu — Tue, 01 Sep 2020 14:21:26 GMT

We are currently trying to measure a distance of 60 m with the AD-FMCLIDAR1-EBZ.
However, we think that FISBA's Laser custom lens is necessary to measure 60m.

Is FISBA's custom lens proven to measure 60m?
Is FISBA or its 3rd party providing custom lenses?

If not, is 3D CAD data available?

Thank you

Channel Order in case of auto mode sequencer

kazics2001 — Thu, 27 Aug 2020 05:01:06 GMT

We are currently evaluating the performance of the AD-FMCLIDAR1-EBZ using the following source code.

github.com/.../lidar.py

At this time, when data is acquired with fmclidar1.rx(), it is returned in an unintended order.

Which data of APD(Avalanche PhotoDiode) C1-C16 corresponds to the data acquired by fmclidar1.rx() in the following settings?

channel_sequencer_opmode = auto

channel_sequencer_order_auto_mode = 0 1 2 3

Are they stored in the order of C2, C4, C13, C15, C6, C8, C9, C11, C10, C12, C5, C7, C14, C16, C1, C3?

AD-FMCLIDAR1-EBZ bringing up issues

ADIApproved — Fri, 21 Aug 2020 13:00:49 GMT

Our customer bought an AD-FMCLIDAR1-EBZ board and met some problems regarding bring up. Would you please help to support? Thanks.

Customer used ZC706+AD-FMCLIDAR1-EBZ this LIDAR development kit and they followed the step of the "Setting up the system”,everyting was ok until i implemented the last step“After the FPGA(EVAL-TPG-ZYNQ3 instead of ZC706) boots the IIO Oscilloscope will start allowing to configure the system, capture and visualize data from it”。They connected the FPGA to the computer with a network cable. However,the IIO Oscilloscope software(Version 0.11) always shows“NO iio devices found”,AD-FMCLIDAR1-EBZ can't be found。

They tested al the power and clk signal on DAQ board and it seems all are normal. FPGA INIT LED and DONE LED is lightened. However, no driven signals in lasers.

Can the AD-FMCLIDAR1-EBZ work with an LPC connector?

Mohamed Faris — Thu, 09 Jul 2020 20:30:41 GMT

Hi,

Can the AD-FMCLIDAR1-EBZ work with an LPC connector? Knowing that FPGAs used are Xilinx ZC 702 and ZUC 104 boards.

Best regards,

How to make and run the lidar.py

emesjx — Wed, 13 May 2020 12:47:44 GMT

In the last section of setting up the system (https://wiki.analog.com/resources/eval/user-guides/ad-fmclidar1-ebz/system_evaluation), we can use " lidar.py " to make some actual distance measurements, how to make and run this application after the system power on ?

thanks!

IIO Oscilloscope without LIDAR plugin

emesjx — Wed, 13 May 2020 12:36:26 GMT

1. I follow the instruction from https://wiki.analog.com/resources/eval/user-guides/ad-fmclidar1-ebz/system_evaluation to set up the lidar system.

2. Connect AD-FMCLIDAR1-EBZ to zc706 kit (https://www.xilinx.com/products/boards-and-kits/ek-z7-zc706-g.html)

3. Use the SD card comes with the kit, copy the BOOT.bin, devicetree.dtb and uImage from the subdirectory "zynq-zc706-adv7511-fmclidar1" to the root of BOOT.

4. Insert the SD card which AD-FMCLIDAR1-EBZ provided to start the system.

However, after running the system. the LIDAR plugin is not shown on the ADI IIO Oscilloscope(only Debug and DMM two plugins) ,AD-FMCLIDAR1-EBZ cannot be test!

Why?