• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 9 subscribers
  • Views 661 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.

AFE7950: adcDacSync in C library is different from Latte log file

Yoonsun Kim
Expert 1740 points
Part Number: AFE7950

Hi,

I checked adcDacSync function of C-library from TI and compared with Latte log file.

The register setting sequence and value are not same each other. The last value of 0x0077 is 0x04 in C-code, but 0x00 in Latte log file.

There are no descriptions about register 76h, 77h and 82h on TRM document, so I have no idea if this difference is not big deal or not. 

C function --->

//START: Leaking Sysref To Dig
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0015, 0x01, 0, 7)); //pll=0x1; Address(0x15[7:0])
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0077, 0x08, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0082, 0x0c, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0077, 0x0b, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0076, 0xff, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0077, 0x0b, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0077, 0x0f, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0077, 0x07, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0082, 0x00, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0077, 0x04, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0076, 0x00, 0, 7));
AFE_FUNC_EXEC(afeSpiWriteWrapper(afeId, 0x0015, 0x00, 0, 7)); //pll=0x0; Address(0x15[7:0])

Latte log file --->

SPIWrite 0015,00,0,7 //digtop=0x0; Address(0x15[7:6])
SPIWrite 0015,01,0,7 //pll=0x1; Address(0x15[7:0])
SPIWrite 0077,08,0,7 //Property_54h_27_27=0x1; Address(0x77[7:3])
SPIWrite 0082,0c,0,7 //Property_60h_21_18=0x3; Address(0x82[7:2])
SPIWrite 0077,0b,0,7 //Property_54h_25_16=0x3ff; Address(0x76[1:0],0x77[7:0])
SPIWrite 0076,ff,0,7
SPIWrite 0077,0b,0,7 //Property_54h_26_26=0x0; Address(0x77[7:2])
SPIWrite 0077,0f,0,7 //Property_54h_26_26=0x1; Address(0x77[7:2])
SPIWrite 0077,0b,0,7 //Property_54h_26_26=0x0; Address(0x77[7:2])
SPIWrite 0077,03,0,7 //Property_54h_27_27=0x0; Address(0x77[7:3])
SPIWrite 0082,00,0,7 //Property_60h_21_18=0x0; Address(0x82[7:2])
SPIWrite 0077,00,0,7 //Property_54h_25_16=0x0; Address(0x76[1:0],0x77[7:0])
SPIWrite 0076,00,0,7

Regards,

YS

  • 0
    TI__Genius 11940 points

    Hi YS,

    Our team is looking into this and we should have an answer by the beginning of next week. 

    Regards,

    David Chaparro

  • 0 in reply to David Chaparro
    TI__Genius 11940 points

    Hi YS,

    I have tested this and found the same issue. I have reached out to our software team and I am waiting for their response on this issue. I hope to have an answer by Monday.

    Regards,

    David Chaparro

  • 0 in reply to David Chaparro
    TI__Genius 11940 points

    Hi YS,

    The latest installer for the AFE79xx GUI includes the updated CAFE library. You can install the latest GUI, TI-AFE79xx-Latte_v2p0p7, and access the CAFE functions in the library folder. 

    We are working on generating the supporting documents and plan to have them uploaded in the AFE79xx secure folder by then end of the week. 

    Regards,

    David Chaparro

  • 0 in reply to David Chaparro
    Expert 1740 points

    Hi David,

    I downloaded the latest GUI,  TI-AFE79xx-Latte_v2p0p7 and found that the struct for afe79xx was chaged from afeSystemParamsStruct to afe79SystemParamsStruct.

    1> The problem is that new GUI still creates old-version parameter when I run AFE.saveCAfeParamsFile().

    2> I have a question ablut USE_AFE79_LIB_FORMAT_2. Under what condition should I define it ?

    Regards,

    YS

  • 0 in reply to Yoonsun Kim
    TI__Genius 11940 points

    Hi YS,

    1. I will test this on my setup and if I see the same issue I will forward this to the software team.

    2. I will check with our software team to see if we have a defined use case for USE_AFE79_LIB_FORMAT_2. I believe that is has something to do with using the CAFE functions through Latte, but I want to double check with the software team. 

    Regards,

    David Chaparro

  • 0 in reply to David Chaparro
    TI__Genius 11940 points

    Hi YS,

    1. After checking the documentation I found that the structure does seem to be named different than the C functions expect. I am working with our team to fix this in the next update.

    2.  Defining USE_AFE79_LIB_FORMAT_2 changes the way you pass the corresponding afe79InstDeviceInfo instance to the functions or the index of the AFE. If USE_AFE79_LIB_FORMAT_2 is defined then the instances of afe79InstDeviceInfo should be defined as an array tiAfe79DeviceInfo_t and the corresponding AFE index should be passed to the functions. If not defined then the corresponding pointer of the afe79InstDeviceInfo should be passed to all the functions.  

    Regards,

    David Chaparro

  • 0 in reply to David Chaparro
    Expert 1740 points

    Hi David,

    Can you share your approximate update schedule ?

    Regards,

    YS

  • 0 in reply to Yoonsun Kim
    TI__Genius 11940 points

    Hi Yoonsun,

    I am waiting on a timeline from our software team, but I would expect it to take at approximately 2 weeks as they are verifying other changes. 

    For now I would suggest updating the name of the structure manually and it will work with the updated CAFE functions, which are also in the AFE79xx secure folder. 

    Regards,

    David Chaparro