• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 48 subscribers
  • Views 636 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Loading custom firmware onto TSW1400

Daaf Sandkuijl
Prodigy 225 points

Other Parts Discussed in Thread: DAC34SH84

Hi,

After receiving the Verilog code for TSW1400 + DAC34SH84 from Ebenezer a few weeks back, I first compiled the code as-is using Quartus 13.1, and loaded it onto the TSW1400 simply by loading the raw bit file (.rbf) through the GUI. That doesn't work, it loads the firmware but then states that no firmware was loaded. I did modify the DAC34SH84.ini file to point to the "tsw1400_top" file instead of the "DAC_SAMPLE_WISE", so the GUI loaded my compiled file automatically, but it still did not recognize is as proper firmware once loaded.

The compiled .rbf file is also significantly smaller than the ones that came with the HSDCPro GUI, about 2 MB compared to 5.8 MB for the other bit files. Should the project that I was sent compile into a usable firmware bit file, or is something else required? Thanks again,

Daaf

  • 0
    TI__Genius 12965 points

    Daaf,

    We don't typically have the BW to support custom firmwares for our evaluation tools, and only provide our source code with that caveat.  However I think this case may be a simple issue.

    The HSDC Pro works hand in hand with the default firmwares.  In the default provided firmwares there are ID registers that hold firmware IDs which HSDC Pro checks upon loading the firmware.  This is for the software to know which firmware has been loaded into the TSW1400 hardware.  If your intention is for your custom firmware to work along with HSDC Pro then you need to follow these dependencies.

    If you are creating custom firmware, HSDC Pro may report back that it found no valid firmware - this is expected since you also need to change the TSW100_IID_Lookup.csv to add an entry for tsw1400_top with an interface ID of 129 - the same as the DAC_SAMPLE_WISE.  When you changed the ini you needed to make sure you added this to the id file.  Or you can leave the ini/ID file alone, and just rename and replace the existing DAC_SAMPLE_WISE.rbf with your custom rbf.

    Ken

  • 0 in reply to Ken C
    TI__Genius 9695 points

    Daaf,

    I am looking into this issue currently and should have the source code for you by early next week.

    Thanks,

    Eben. 

  • 0 in reply to Ken C
    Prodigy 225 points

    Hi Ken,

    Thanks for the quick reply. I simply named my bitfile DAC_SAMPLE_WISE.rbf to avoid the .ini and .csv file issues, and the GUI loads its onto the TSW1400 alright (as before), but right after that it still says that no firmware has been loaded. Somehow the code or Quartus project that I have doesn't compile to the same bitfile as the one that generated DAC_SAMPLE_WISE.rbf. I have a feeling those registers you mention have something to do with it, would they have been defined in the Quartus archived project that Ebenezer sent, or do they need to be set still?

    Thanks again,

    Daaf

  • 0 in reply to Daaf Sandkuijl
    Prodigy 225 points

    Hi Eben, 

    Thanks, I'm looking forward to it.

    Kind regards,

    Daaf

    P.S. I used Quartus 12.1 for the latest compilation, but have access to Quartus 13.1 as well.