• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 10 subscribers
  • Views 558 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AFE7900EVM: Regarding the bring up issue for FAE7900EVM with ZCU102

Maitry Khambhati
Intellectual 370 points
Part Number: AFE7900EVM
Other Parts Discussed in Thread: AFE7900, AFE7950

Hello support Team,

I have AFE7900EVM+ZCU102 Board and I am following the bring up steps as per the attached word document (TI204c-setup.docx), up to 4th steps , it is working accurate. and we are getting proper logs as per given the  document. In ZCU102 , I am programming the bit file and set the debug probes as per given instructions. during the running of the script(TI_IP_ConfigAfe.py) , at that time , I am getting error of chip version(I have attached the screenshots as well for your reference). Also, One more thing I have observed that in the AFE7900EVM iGui , The AFE7900 part number is not available in the drop down menu. (Please check the screenshot of teh AFE device list). So, when I change any parameter through GUI, I am getting the same error of chip version. FYI, I am using Latte GUI installed from secure folder(AFE79xxEVM_GUIv1p11p6_installer.exe). So, please look into this matter as soon as possible, as our further testing is getting delayed. weather the GUI is not correct or python file has some error?

 

  

TI_IP_ConfigAfe.txt 
## Initiates AFE79xx Bring-up
setupParams.skipLmk	=	True
AFE.deviceBringup()

AFE.TOP.overrideTdd(15,0,15)

#for i in range(4): AFE.DSA.setRxDsa(i,4)

### ADC Ramp Out
# for i in range(3):
# 	AFE.JESD.ADCJESD[0].adcRampTestPattern(i,1,1)
# 	AFE.JESD.ADCJESD[1].adcRampTestPattern(i,1,1) #chNo, En, RampInc

TI204c-Setup.docx

  • 0
    Intellectual 370 points

    Hello support team,

    Further please find attached herewith the full log , If I continue with the chip error. 

    log error_after continue with chip error.txt 
    AFE79xxLibraryPG1p0
spi - USB Instrument created.
resetDevice
Purge
MPSSE mode set
Kintex RegProgrammer - USB Instrument created.
Kintex RegProgrammer - USB Instrument created.
Kintex RegProgrammer - USB Instrument created.
#================ ERRORS:0, WARNINGS:0 ================#
Power Card - USB Instrument created.
Reset the FPGA and try again.
Loaded Libraries
#================ ERRORS:1, WARNINGS:0 ================#
The External Sysref Frequency should be an integer factor of: 1.92MHz
2T2R1F Number: 0
Valid Configuration: True
laneRateRx: 12165.12
laneRateFb: 12165.12
laneRateTx: 12165.12
2T2R1F Number: 1
Valid Configuration: True
laneRateRx: 12165.12
laneRateFb: 12165.12
laneRateTx: 12165.12
LMK Clock Divider - Device registers reset.
LMK Clock Divider - Device registers reset.
REFCLOCK is used from LMK source, ensure board connections are ok to do the same
#================ ERRORS:0, WARNINGS:1 ================#
The External Sysref Frequency should be an integer factor of: 1.92MHz
2T2R1F Number: 0
Valid Configuration: True
laneRateRx: 12165.12
laneRateFb: 12165.12
laneRateTx: 12165.12
2T2R1F Number: 1
Valid Configuration: True
laneRateRx: 12165.12
laneRateFb: 12165.12
laneRateTx: 12165.12
Device Initialization for ChipVersion: 2.0
DONOT_OPEN_Atharv_FULL - Device registers reset.
Mismatch between Entered (0x20) and device Read Chip Version(0x12 or 0x13). Please select correct Chip Version.
#Error: invalid syntax (string, line 2)
# "", line 3, in 
# File "C:\Users\Asus\Documents\Texas Instruments\Latte\lib\\AFE79xxLibraries\\AFE79xxLibraryPG1p0\resourceFiles\mFuncDecorator.py", line 88, in inDecorator
# a=func(*args,**kwargs)
# File "C:\Users\Asus\Documents\Texas Instruments\Latte\lib\\AFE79xxLibraries\\AFE79xxLibraryPG1p0\mAfeLibrary.py", line 247, in deviceBringup
# self.softReset()
# File "C:\Users\Asus\Documents\Texas Instruments\Latte\lib\\AFE79xxLibraries\\AFE79xxLibraryPG1p0\resourceFiles\mFuncDecorator.py", line 88, in inDecorator
# a=func(*args,**kwargs)
# File "core\asterixExecGUI.py", line 1814, in runBuffer
# File "", line 2
# setupParams.skipLmk = True
# ^
# SyntaxError: invalid syntax
# 
# 
#================ ERRORS:1, WARNINGS:0 ================#
SPIA has got control of PLL pages
PLL Pages SPI control relinquished.
SPIA has got control of PLL pages
PLL Pages SPI control relinquished.
###########Device DAC JESD-RX 0 Link Status###########
Comma Align Lock Lane0: False; Please check if the transmitter is sending data and eye is good.
Comma Align Lock Lane1: False; Please check if the transmitter is sending data and eye is good.
Comma Align Lock Lane2: False; Please check if the transmitter is sending data and eye is good.
Comma Align Lock Lane3: False; Please check if the transmitter is sending data and eye is good.
CS State TX0: 0b00000000 . It is expected to be 0b10101010
BUF State TX0: 0b11111111 . It is expected to be 0b11111111
Couldn't get the link up for device RX: 0; Alarms: 0xc0
###################################
###########Device DAC JESD-RX 1 Link Status###########
Comma Align Lock Lane0: False; Please check if the transmitter is sending data and eye is good.
Comma Align Lock Lane1: False; Please check if the transmitter is sending data and eye is good.
Comma Align Lock Lane2: False; Please check if the transmitter is sending data and eye is good.
Comma Align Lock Lane3: False; Please check if the transmitter is sending data and eye is good.
CS State TX0: 0b00000000 . It is expected to be 0b10101010
BUF State TX0: 0b11111111 . It is expected to be 0b11111111
Couldn't get the link up for device RX: 1; Alarms: 0xc0
###################################
#================ ERRORS:10, WARNINGS:0 ================#

  • 0 in reply to Maitry Khambhati
    Intellectual 370 points

    Hello support team,

    Request you to provide feedback as soon as possible.

  • 0 in reply to Maitry Khambhati
    TI__Guru* 91947 points

    Maitry,

    We are looking into this.

    Regards,

    Jim

  • 0 in reply to jim s
    Intellectual 370 points

    Hello,

    Request you to provide details as soon as possible, as our further testing is getting delayed due to this.

  • 0 in reply to Maitry Khambhati
    TI__Genius 11960 points

    Hi Maitry,

    This issue is occurring because of a mismatch in the chip version in the setup.py script. For all AFE795x devices in setup.py chipVersion=0x13. For all AFE790x devices in setup.py chipVersion=0x20. 

    Please note that this issue is taken care of when using the respective AFE7900 or AFE7950 folders in the AFE79xx secure folder. We recommend using the scripts from the folder of the device you plan to use. 

    Regards,

    David Chaparro