Post Go back to editing

how to change the IP address of Zync platform (EVAL-TPG-ZYNQ3).

Product Number: ARDV9009 evaluation board

Hi,

my name is Haim Litvak

I works with EVB of ADRV9009

I want to know how to change the IP address of Zync platform (EVAL-TPG-ZYNQ3).

Please advise

Thanks

Haim

Parents Reply
  • May be I need to change some jumpers in board, In order to insert the boot parameters or environments of this SW?

    No need of changing any parameters or environment in the SW .

    Once the board is booted ,connect through Serial port and once you get the console .

    Go to vi/etc/network/interfaces and  Comment out the line 'iface eth0 inet dhcp' with a '#'.

    Add the following lines:

    iface eth0 inet static

    address 192.168.1.10

    netmask 255.255.255.0

    gateway 192.168.1.1

    Save changes.

    Reboot platform and check that the correct IPv4 address has been assigned properly .

    Refer to Can't Ping FPGA section for details .

     TES Connection Issues 

Children
  • Hi,

    I have evb "EVAL-TPG-ZYNQ3 " could you send me please the user guide for this card.

    I want to know which serial port to use

    I connected to mini USB port that located in the same side as ETH port to manage of card.

    After power up I see:

    "Xilinx Zync-7000 All Programmable SoC ZC706 Evaluation Kit"

    and in menu below: for "PS" and "PL"

    May be problem with:

    1. SD card (TES SW)

    2. jumpers in pcb of EVAL - TPG-ZYNQ3?

    3. connected to wrong serial port?

    Could you send me please the user guide for EVAL - TPG-ZYNQ3 with reference number of serial port? Or picture with correct serial port

    Thanks

    Haim

  • The issue might be due to SD card , can you try reflashing the Image . Download the SD Card image from the below link .

    https://www.analog.com/en/design-center/landing-pages/001/transceiver-evaluation-software.html

     Follow the programming instructions from the below link .

    https://wiki.analog.com/resources/tools-software/linux-software/zynq_images/windows_hosts

    Once your SD card is ready ,then connect to the Serial port (pointed in the screenshot below ) to J21 in the ZYNQ3 board or else you can try connecting to ethernet port , Login to mobaxterm with the default  IP first and then change the IP address by going to  vi/etc/network/interfaces file .

  • Hi,

    I think that I succeeded to load the "TES" image EVB from SD card. The problem was in setting of Switches SW11(3,4 - should be 1) and 1,2,5 =0.

    I want to verify that TES image loaded and run "OK". Please advise how to verify. In attached files I send you the "u-boot" boot parameters and "ubuntu" recording.

    I changed the IP of  EVB by command "ifconfig". I tested the settings by sending the "ping" command from PC. It works "OK"

    I started application "GUI TES" in PC, set the IP of EVB board and then tried to connect, but connection "Failed"

    I verify that "Firewall switched OFF".

    May be need to set the new IP address for HOST in EVB? (The default HOST IP is 192.168.1.2)

    
    U-Boot 2014.01-dirty (Jul 21 2014 - 14:45:35)
    
    I2C:   ready
    Memory: ECC disabled
    DRAM:  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:  0
    Device: zynq_sdhci
    Manufacturer ID: 74
    OEM: 4a60
    Name: SDU1
    Tran Speed: 50000000
    Rd Block Len: 512
    SD version 3.0
    High Capacity: Yes
    Capacity: 14.7 GiB
    Bus Width: 4-bit
    reading uEnv.txt
    379 bytes read in 7 ms (52.7 KiB/s)
    Loaded environment from uEnv.txt
    Importing environment from SD ...
    Running uenvcmd ...
    Copying Linux from SD to RAM...
    reading uImage
    2999904 bytes read in 289 ms (9.9 MiB/s)
    reading devicetree.dtb
    11848 bytes read in 15 ms (770.5 KiB/s)
    reading uramdisk.image.gz
    ** Unable to read file uramdisk.image.gz **
    ## Booting kernel from Legacy Image at 03000000 ...
       Image Name:   Linux-3.14.0-g5ea3bc9
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2999840 Bytes = 2.9 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 1fffa000, end 1ffffe47 ... OK
    
    Starting kernel ...
    
    Uncompressing Linux... done, booting the kernel.
    Booting Linux on physical CPU 0x0
    Linux version 3.14.0-g5ea3bc9 (jeckard@hotel.adral.analog.com) (gcc version 4.7.3 (Sourcery CodeBench Lite 2013.05-40) ) #1 SMP PREEMPT Thu May 1 08:26:35 EDT 2014
    CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
    CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine model: Xilinx Zynq ZC706
    bootconsole [earlycon0] enabled
    cma: CMA: reserved 40 MiB at 2d000000
    Memory policy: Data cache writealloc
    PERCPU: Embedded 7 pages/cpu @ec7c8000 s7680 r8192 d12800 u32768
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 260624
    Kernel command line: console=ttyPS0,115200 root=/dev/mmcblk0p2 rw earlyprintk rootfstype=ext4 rootwait
    PID hash table entries: 4096 (order: 2, 16384 bytes)
    Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
    Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
    Memory: 992360K/1048576K available (3984K kernel code, 213K rwdata, 1512K rodata, 183K init, 126K bss, 56216K reserved, 270336K highmem)
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
        lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
        modules : 0xbf000000 - 0xbfe00000   (  14 MB)
          .text : 0xc0008000 - 0xc0566420   (5498 kB)
          .init : 0xc0567000 - 0xc0594e00   ( 184 kB)
          .data : 0xc0596000 - 0xc05cb400   ( 213 kB)
           .bss : 0xc05cb40c - 0xc05eacd4   ( 127 kB)
    Preemptible hierarchical RCU implementation.
            Dump stacks of tasks blocking RCU-preempt GP.
            RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
    RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
    NR_IRQS:16 nr_irqs:16 16
    slcr mapped to f0004000
    zynq_clock_init: clkc starts at f0004100
    Zynq clock init
    sched_clock: 16 bits at 54kHz, resolution 18432ns, wraps every 1207951633ns
    timer #0 at f0006000, irq=43
    Console: colour dummy device 80x30
    Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328)
    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: thread -1, cpu 0, socket 0, mpidr 80000000
    Setting up static identity map for 0x3c3eb8 - 0x3c3eec
    L310 cache controller enabled
    l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB
    CPU1: Booted secondary processor
    CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
    Brought up 2 CPUs
    SMP: Total of 2 processors activated.
    CPU: All CPU(s) started in SVC mode.
    devtmpfs: initialized
    VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
    regulator-dummy: no parameters
    NET: Registered protocol family 16
    DMA: preallocated 256 KiB pool for atomic coherent allocations
    syscon f8000000.slcr: regmap [mem 0xf8000000-0xf8000fff] registered
    hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
    hw-breakpoint: maximum watchpoint size is 4 bytes.
    bio: create slab <bio-0> at 0
    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
    Linux video capture interface: v2.00
    Advanced Linux Sound Architecture Driver Initialized.
    Switched to clocksource ttc_clocksource
    NET: Registered protocol family 2
    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)
    TCP: reno registered
    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: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
    futex hash table entries: 512 (order: 3, 32768 bytes)
    bounce pool size: 64 pages
    msgmni has been set to 1490
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208
    dma-pl330 f8003000.ps7-dma:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
    ▒▒k▒▒▒▒[ttyPS0] enabledt MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps
    console [ttyPS0] enabled
    bootconsole [earlycon0] disabled
    bootconsole [earlycon0] disabled
    [drm] Initialized drm 1.1.0 20060810
    drivers/gpu/drm/adi_axi_hdmi/axi_hdmi_drv.c:axi_hdmi_platform_probe[176]
    platform 70e00000.axi_hdmi: Driver axi-hdmi requests probe deferral
    brd: module loaded
    loop: module loaded
    cdns-spi e0006000.spi: at 0xE0006000 mapped to 0xF0016000, irq=58
    cdns-spi e0007000.spi: at 0xE0007000 mapped to 0xF0018000, irq=81
    libphy: XEMACPS mii bus: probed
    xemacps e000b000.eth: pdev->id -1, baseaddr 0xe000b000, irq 54
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ULPI transceiver vendor/product ID 0x0424/0x0007
    Found SMSC USB3320 ULPI transceiver.
    ULPI integrity check: passed.
    zynq-ehci zynq-ehci.0: Xilinx Zynq USB EHCI Host Controller
    zynq-ehci zynq-ehci.0: new USB bus registered, assigned bus number 1
    zynq-ehci zynq-ehci.0: irq 53, io mem 0x00000000
    zynq-ehci zynq-ehci.0: USB 2.0 started, EHCI 1.00
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    usbcore: registered new interface driver usb-storage
    usbcore: registered new interface driver usbserial
    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
    mousedev: PS/2 mouse device common for all mice
    i2c /dev entries driver
    i2c i2c-0: Added multiplexed i2c bus 1
    i2c i2c-0: Added multiplexed i2c bus 2
    at24 3-0054: 1024 byte 24c08 EEPROM, writable, 1 bytes/write
    i2c i2c-0: Added multiplexed i2c bus 3
    i2c i2c-0: Added multiplexed i2c bus 4
    rtc-pcf8563 5-0051: chip found, driver version 0.4.3
    rtc-pcf8563 5-0051: low voltage detected, date/time is not reliable.
    rtc-pcf8563 5-0051: rtc core: registered rtc-pcf8563 as rtc0
    i2c i2c-0: Added multiplexed i2c bus 5
    at24 6-0050: 256 byte 24c02 EEPROM, writable, 1 bytes/write
    i2c i2c-0: Added multiplexed i2c bus 6
    i2c i2c-0: Added multiplexed i2c bus 7
    i2c i2c-0: Added multiplexed i2c bus 8
    pca954x 0-0074: registered 8 multiplexed busses for I2C switch pca9548
    sdhci: Secure Digital Host Controller Interface driver
    sdhci: Copyright(c) Pierre Ossman
    sdhci-pltfm: SDHCI platform and OF driver helper
    mmc0: no vqmmc regulator found
    mmc0: no vmmc regulator found
    mmc0: SDHCI controller on e0100000.sdhci [e0100000.sdhci] using ADMA
    platform leds.2: Driver leds-gpio requests probe deferral
    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
    adv7511-hdmi-snd adv7511_hdmi_snd.6: adv7511 <-> 75c00000.axi-spdif-tx mapping ok
    mmc0: new high speed SDHC card at address 59b4
    TCP: cubic registered
    NET: Registered protocol family 17
    Registering SWP/SWPB emulation handler
    mmcblk0: mmc0:59b4 SDU1  14.7 GiB
    regulator-dummy: disabling
     mmcblk0: p1 p2
    axi-hdmi 70e00000.axi_hdmi: No connectors reported connected with modes
    [drm] Cannot find any crtc or sizes - going 1024x768
    Console: switching to colour frame buffer device 128x48
    axi-hdmi 70e00000.axi_hdmi: fb0:  frame buffer device
    axi-hdmi 70e00000.axi_hdmi: registered panic notifier
    [drm] Initialized axi_hdmi_drm 1.0.0 20120930 on minor 0
    platform leds.2: Driver leds-gpio requests probe deferral
    rtc-pcf8563 5-0051: low voltage detected, date/time is not reliable.
    rtc-pcf8563 5-0051: setting system clock to 2010-08-02 07:08:34 UTC (1280732914)
    ALSA device list:
      #0: HDMI monitor
    EXT4-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
    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: 180K (c0567000 - c0594000)
    ▒▒+▒▒ ureadahead main process (738) terminated with status 5
    Last login: Mon Aug  2 03:07:05 EDT 2010 on tty1
    Welcome to Linaro 12.11 (GNU/Linux 3.14.0-g5ea3bc9 armv7l)
    
     * Documentation:  https://wiki.linaro.org/
    
    root@linaro-ubuntu-desktop:~#
    
    zynq-uboot> print
    baudrate=115200
    bitstream_image=system.bit.bin
    boot_image=BOOT.bin
    boot_size=0xF00000
    bootcmd=run $modeboot
    bootdelay=3
    bootenv=uEnv.txt
    devicetree_image=devicetree.dtb
    devicetree_size=0x20000
    ethact=Gem.e000b000
    ethaddr=00:0a:35:00:01:22
    fdt_high=0x20000000
    importbootenv=echo Importing environment from SD ...; env import -t ${loadbootenv_addr} $filesize
    initrd_high=0x20000000
    ipaddr=10.10.70.102
    jtagboot=echo TFTPing Linux to RAM... && tftpboot 0x3000000 ${kernel_image} && tftpboot 0x2A00000 ${devicetree_image} && tftpboot 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000
    kernel_image=uImage
    kernel_size=0x500000
    loadbit_addr=0x100000
    loadbootenv=fatload mmc 0 ${loadbootenv_addr} ${bootenv}
    loadbootenv_addr=0x2000000
    mmc_loadbit_fat=echo Loading bitstream from SD/MMC/eMMC to RAM.. && mmcinfo && fatload mmc 0 ${loadbit_addr} ${bitstream_image} && fpga load 0 ${loadbit_addr} ${filesize}
    modeboot=sdboot
    nandboot=echo Copying Linux from NAND flash to RAM... && nand read 0x3000000 0x100000 ${kernel_size} && nand read 0x2A00000 0x600000 ${devicetree_size} && echo Copying ramdisk... && nand read 0x2000000 0x620000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000
    norboot=echo Copying Linux from NOR flash to RAM... && cp.b 0xE2100000 0x3000000 ${kernel_size} && cp.b 0xE2600000 0x2A00000 ${devicetree_size} && echo Copying ramdisk... && cp.b 0xE2620000 0x2000000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000
    qspiboot=echo Copying Linux from QSPI flash to RAM... && sf probe 0 0 0 && sf read 0x3000000 0x100000 ${kernel_size} && sf read 0x2A00000 0x600000 ${devicetree_size} && echo Copying ramdisk... && sf read 0x2000000 0x620000 ${ramdisk_size} && bootm 0x3000000 0x2000000 0x2A00000
    ramdisk_image=uramdisk.image.gz
    ramdisk_size=0x5E0000
    rsa_jtagboot=echo TFTPing Image to RAM... && tftpboot 0x100000 ${boot_image} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
    rsa_nandboot=echo Copying Image from NAND flash to RAM... && nand read 0x100000 0x0 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
    rsa_norboot=echo Copying Image from NOR flash to RAM... && cp.b 0xE2100000 0x100000 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
    rsa_qspiboot=echo Copying Image from QSPI flash to RAM... && sf probe 0 0 0 && sf read 0x100000 0x0 ${boot_size} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
    rsa_sdboot=echo Copying Image from SD to RAM... && fatload mmc 0 0x100000 ${boot_image} && zynqrsa 0x100000 && bootm 0x3000000 0x2000000 0x2A00000
    sdboot=if mmcinfo; then run uenvboot; echo Copying Linux from SD to RAM... && fatload mmc 0 0x3000000 ${kernel_image} && fatload mmc 0 0x2A00000 ${devicetree_image} && if fatload mmc 0 0x2000000 ${ramdisk_image}; then bootm 0x3000000 0x2000000 0x2A00000; else bootm 0x3000000 - 0x2A00000; fi; fi
    serverip=10.10.70.101
    stderr=serial
    stdin=serial
    stdout=serial
    uenvboot=if run loadbootenv; then echo Loaded environment from ${bootenv}; run importbootenv; fi; if test -n $uenvcmd; then echo Running uenvcmd ...; run uenvcmd; fi
    usbboot=if usb start; then run uenvboot; echo Copying Linux from USB to RAM... && fatload usb 0 0x3000000 ${kernel_image} && fatload usb 0 0x2A00000 ${devicetree_image} && fatload usb 0 0x2000000 ${ramdisk_image} && bootm 0x3000000 0x2000000 0x2A00000; fi
    
    Environment size: 3412/131068 bytes
    zynq-uboot>
    

    If yes, please advise how perform this

  • I changed the IP of  EVB by command "ifconfig"

    You can be able to see the IP Address set through ifconfig . If you are changing the IP Address go to  vi/etc/network/interfaces file, change the IP , restart the board once , Check the ping and then try connecting to the TES GUI.

    Still if you see any issue ,check with the default Host IP  first . Try connecting directly through LAN to your PC/Laptop,  Check the ping and then try connecting to the TES GUI. Please check the procedure of how to set the static IP address mentioned in the document .

    Can you share us the snippet of the connection failed error which you are getting while connecting to the TES GUI ?

  • Hi,

    I want to verify that TES application loaded OK

    After loading of Image, I see in Seral port  "root@linaro-ubuntu-desktop:~#". According with procedure that you send me in attached link after load of image I see the prompt: "root@analog:~#". Please advise is it "OK"

    I set the command "ps" in Putty terminal, in order to verify if any process is "run" - no process running.

    I have access by SSH and see the folders in Linux.

    May be need to perform some command in order to run the system?

  • I hope you are waiting for 3 to 5 minutes once you turn on the board to make sure that the image loads properly and then try connecting with the TES GUI.

    Can you uninstall and install the TES GUI again and try connecting. 

    Can you try checking whether the two LED's (D501 and D502) on the Eval Board  are on?

    Once you are connected , Update the platform files by navigating to Tools > Update >Platform Files. The TES automatically updates files on the Zynq SD card and reboots the ADRV board .

    First try with the default IP first , and with port number 55555.  Can you share us the snippet of the connection failed error which you are getting while connecting to the TES GUI ?

  • Hi Vanitha,

    I succeed to connect to EVB from stand alone PC that not connected to Network.

    I used the IP address according with user guide. TES EVB IP: 192.168.1.10, TES SW in PC IP is: 192.168.1.2

    In the future, could you verify please how to connect from EVB TES SW (ZYNQ707 board) to PC SW TES with other address than appears in user guides. I suggest to test this procedure in your setup, before send to me.

    Thanks

    Haim

  • Hi Vanitha,

    I started to test the RX 1 path of EV board of ADRV9009.

    I set the signal generator to Freq. =1.801GHz with Pout=-9dBm (-9dBm should be Full Scale Power input according with Data sheet) and connect the output of Signal Generator to RX1 of ADRV9009.(Ref. Clock and Tallise loaded successfully- according with LED's in ZYNQ and ADRV9009)

    In Tallise: RX path: the RX 1 LO Frequency=1.8GHz,

    RX 1 Gain Table Index =255 (0 attenuation, or maximal Gain).

    I received the in GUI the "Fund Freq"=1MHz -  tone with Power =-21dBFS. The expected Power is ~-1 or 2dB from Full Scale

    Could you explain please?

    Thanks

    Haim

  • It seems that you are not getting expected power level at the output of the ADRV9009 Receiver .

    Are you checking with CW tone or modulated signal ? 

    Can you try checking with 1810MHz signal i.e.  10MHz away from LO .

    Can you test at -15dBm, -20dBm power level  and read the RX DEC power at each case. 

    Also can you try reading back the RX1 gain index set ?

  • Hi Vanitha,

    I detected the "root cause" of the problem with RX Power Input. The problem was in RF cable. I replaced the RF cable. 

    After replaced the RF cable I received the expected Power Input levels.

    For Pin=-9dBm and RX 1 Gain Index=255, I received the ~0dBFS, and in time scale: I , Q Levels=~+/-32000. For CW=1MHz and 10MHz.

    Thanks

    Haim