• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 9 subscribers
  • Views 666 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.

DAC38RF82: We are not able use to IBIS AMI file given to us. (DAC38RF82)

Rajesh khanna
Intellectual 690 points
Part Number: DAC38RF82
Other Parts Discussed in Thread: DAC38J84, ADC12DJ3200

Hi,

we have issue with the ibis ami file given to us in the following link.

The file is not compatible with DAC38RF82 it is showing DAC38j84. when we try import using mentor hyperlynx the pin is not compatible with the device.

Kindly provide the right IBIS AMI file for our signal integrity simulation.

Regards,

Rajesh khanna.

  • 0
    TI__Guru* 91947 points

    Rajesh,

    Both parts use the same serdes interface. This model is valid for both parts.

    Regards,

    Jim

     

  • 0 in reply to jim s
    Intellectual 690 points

    Hi Jim,

    The serdes internally may be same, the two chips not having pin compatibility also.

    When we import our layout into the SI tool, it is not allowing as pins are different.

    Regards,

    Rajesh khanna

  • 0 in reply to Rajesh khanna
    TI__Guru* 91947 points

    dac38rf80.ibsRajesh,

    See if this package model helps.

    Regards,

    Jim

  • 0 in reply to jim s
    Intellectual 690 points

    Hi,

    The file you have given is ibis only we need ibis ami file.

    as the SI tool, hyperlynx is expecting ami model. 

    Regards,

    Rajesh khanna 

  • 0 in reply to Rajesh khanna
    TI__Guru* 91947 points

    Rajesh,

    I am not 100% sure we can provide what you need. The IBIS information we have is a combination of the two parts. Maybe with some editing, you can create the model you need. Everything currently available can be found from the file you can download from the link below.

    Included is the package model for the DAC38J84, again not the same device, however it is the same plastic package and IBIS-AMI model as the DAC38RF8x. You can open either the .s16p or .s32p files and see the port naming which is pretty intuitive (example below).

     

    !   PORT#     PORT_NAME  NET_NAME

    ! PORT1:  RXN0_BGA.H1_GND RXN0

    ! PORT2:  RXN0_DIE.19_GND RXN0

    ! PORT3:  RXN1_BGA.J1_GND RXN1

     

    Regards,

     

    Jim

     

    txn.box.com/.../vdoau7ycg8p89nd47g5r40c2zqdqq52k

  • 0 in reply to jim s
    Intellectual 690 points

    Hi Jim,

    We tried to modify the IBIS AMI model for DAC38J84, but we are not able to make the model work. We also found the VinL and VinH provided in the IBIS AMI file was wrong after interchanging the values model started importing into he tool.

    Here by i am sharing the eye diagram we obtained after editing. We were able to perform simulation for ADC12DJ3200 with the xilinx FPGA since the model's were provided by TI.

    We have changed the DAC from analog devices AD9162/64 to DAC38RF82 owing to better performance and support we were getting from TI.

    Request you to kindly extended the support by providing the CORRECT IBIS AMI model for the device we have chosen, our customer does not want to compromise.

    He wanted the SI to be performed and we are struck at this Stage.

    Regards,

    Rajesh khanna.

  • 0 in reply to Rajesh khanna
    TI__Guru* 91947 points

    Rajesh,

    Unfortunately, we do not have the resources to work on this right now. There are plans to get this corrected but this will probably not happen until second quarter of this year.

    Regards,

    Jim

  • 0 in reply to jim s
    Intellectual 690 points

    Hi Jim,

    Understand problem currently everyone is facing.

    Thanks for the support.

    Regards,

    Rajesh khanna