TSW1400EVM: How to Extract Raw Data, without using the HSDC Pro GUI (using a Linux based GPU)?

Devaganthan,

I am checking with the software team about this. After downloading HSDC Pro, there are several DLL examples available. These are located at the following location:

C:\Progam files(86) \ Texas Instruments \ High Speed Converter Pro \ HSDC Automation DLL \ Manual and Examples  

See if any of these files help with your application.

The firmware for the TSW1400EVM is available on the TSW1400EVM product folder on the TI website. Modifying the firmware may be another option for you.   

Regards,

Jim

Thanks for a quick and helpful reply Jim!

Are there any updates from the Software team, with regard to the data transfer to an external Linux based GPU?

Regards,

Devaganthan

Devaganthan,

The existing software had built a wrapper DLL which will call the 1400 1.0 Board DLL directly and does the communication. The user can make use of the functions available in the Direct Board Access DLL to communicate to the board. The function prototypes are almost similar to the automation functions. Unfortunately, this DLL was not used by the firmware that supports the ADS54T0x EVM. The team will have to develop a new DLL for this EVM.

To assist with this development, please provide the following info:

1. The software you plan on using with this DLL. Will it be 32 or 64 bit based? 

2. The ADC part number on your EVM.

Once we have this info, it will take a few days to develop and test this new DLL.

Regards,

Jim

Thanks for your reply Jim!

We want to process the raw data from 1400 on our Linux System. What we finally wish to have is the raw data in a CSV File. 

1) We want to connect 1400 with NVIDIA Jetson Devices through the on board USB Port. The device uses a 64-bit CPU, Linux OS (Ubuntu Based). Our end goal is to receive the data from the ports of 1400.

2) ADS54T02EVM – The ADC being used. 

We also want to automate. 

Regards, 

Devaganthan.

We are looking into this.

Thank you Jim.

By when we can hear back from you? A rough date, would help us plan things. 

Regards,

Devaganthan 

Devaganthan,

Our third party software development team is currently preparing to test support for the 0.0 version of the TSW1400 Board DLL with the TSW1400 Board DLL Direct Access DLL, which will work only with the Windows OS.  Due to the holiday season, this may not start until the first week of January.

 Regarding the TSW1400 Board DLL Direct Access support request in Linux, they did a feasibility check and below are the risks and requirements they foresee:

1. To Create Linux project in Visual Studio, they will require a license of an add-on “Visual GDB”. 
2. For testing, they would need to arrange to test a PC with Linux OS, which currently they do not have, with a TSW1400 board with an ADC(which uses 0.0 DLL).
3. They are new to this software technology and might face setbacks/obstacles in development.

 One option we are looking into is having them developing and delivering the .SO files without testing it. Since this is a new software technology and the team is not familiar with it, they don’t have any idea on how well it will work. Depending on the time and cost of this project and If you agree to test this for them, TI might decide to do this approach.

Regards,

Jim

Thank you Jim,

jim s said:

Unfortunately, this DLL was not used by the firmware that supports the ADS54T0x EVM.

Right now it would be helpful if the Direct Access DLL be developed for the ADS54T02 EVM. (Windows OS)

For Linux, are we expected to provide the necessary licenses and boards for the Direct Access development? If so can we have an estimate of the Cost with  the split up. 

We would like to know the Vibration limits or fragility curve details for TSW1400 and ADS54T02. It would be helpful if we could have them at the earliest.

Regards,

Devaganthan

Devaganthan,

Are you saying you can work with an Windows OS version? If so, we should have something available in the next week or so. I will have to check the software team's schedule once they return from holiday break.

We have no vibration or fragility curve details. These boards are designed for lab bench testing, not environmental conditions. 

Regards,

Jim

Thanks for your Reply Jim,

Can we have the conversation further via emails? Can I have your email?

Thanks

Devaganthan S S

Please send yours and I will contact you.

Jim,

I am holding the same specs of ADC and Data Acquisition board. I am trying to automate functions using the scripts under "C:\....\High Speed Data Converter Pro\HSDCPro Automation DLL\Manual and Examples", I tried some automation scripts for Reading from the DDR Memory, etc., in this regard, I was unable to find script or function for implementing the continuous capture functionality.

My basic objective is to capture the data upon each external trigger received to the Data Acquisition board and store it in a file (as a separate file or files obtained on each trigger). In this regard, I tried looping the Read DDR Memory function in the automation script and saving it as a separate file (also by enabling "Arm trigger on next capture" button), but the Read DDR memory takes much longer time to capture the data upon which many of the triggers have already passed. So, one of my backup approach was to implement continuous capture and post process the data by sampling it with respect to the trigger obtained, but as said in the 1st paragraph, I am unable to find a script for continuous capture. 

Is it required to program the FPGA to suit our intended application?. What is the advantage of modifying the firmware and how do we do it?

I request you to help me in this process. Thanks in advance!

Regards,

Adithya.N

Email: adithya.n@galaxeye.space

Jim,

Here are few numbers that I would require, ADC Sampling frequency = 800MHz (which I know the ADS54T0x can provide). The number of samples comes to be around 30k and the repetition frequency is around 1000Hz which means that the data containing the first 30k samples has to be captured and saved to file either in binary or CSV format within 1ms interval so that the next capture phase can begin and store another 30k samples in a new file. 

As an attempt, I used the "C:\....\High Speed Data Converter Pro\HSDCPro Automation DLL\Manual and Examples\Automation DLL C Example\ADC\Automation DLL C Example ADC.vcproj" example and checked the execution time of the function Pass_Capture_Event before looping the function for capturing data in next cycle.  

if (TriggerModeEnable==0)
{
    printf("\n\nStart Normal Capture. Press any key to continue...");
	getch();
	printf("\nStarting Normal Capture...");
	//start clock
	Error_Status = Pass_Capture_Event(TimeoutInMs);
	//stop clock and measure the execution time in milliseconds
	printf("\nError Status = %d", Error_Status);
	printf("\n\nSaving ADC Raw Data as CSV file at %s", CSVFilePathWithName);
    Error_Status = Save_Raw_Data_As_CSV(CSVFilePathWithName, TimeoutInMs);
    printf("\nError Status = %d", Error_Status)
}

The function takes around 250ms which is far beyond our requirement (I used Unix Timestamp for accurate precision). Can you help us with deciding whether the procedure is right? and whether the DAQ can provide us the required numbers (mentioned in the top) that we desire. You can also communicate to my mail ID if desired. Thanks in advance!

Regards,

Adithya N

Email: adithya.n@galaxeye.space