Hello,
First, apologies for posting a few times in the past few days. I figured it would be easier to start a new thread then to try and keep the other one alive. I'm close to being able to begin to develop, but I'm still having difficulties getting firmware on the board. I am using Quartus II to create bit files, and I'm putting them on the board with HSDC Pro. My other post inquiring about JTAG vs USB-JTAG is here:
http://e2e.ti.com/support/data_converters/high_speed_data_converters/f/68/t/354593.aspx
As explained in a few other threads, when you upload a custom firmware using HSDC Pro, you get the following error message:
"No firmware. Please select a device to load firmware to the board."
This, of course, neither confirms or rejects that the firmware has actually made it to the board. My understanding is it only means that the custom firmware will not properly communicate with HSDC Pro. So, to test this, I added the following lines to the end of my project file for verification the firmware is loaded:
assign led[0] = 1'b1;
assign led[1] = 1'b1;
assign led[2] = 1'b0;
assign led[3] = 1'b0;
assign led[4] = 1'b1;
assign led[5] = 1'b1;
assign led[6] = 1'b0;
assign led[7] = 1'b1;
However, when burning the firmware, the LEDs do not light up. I understand that custom firmware isn't really supported, but I'm using source code taken directly from a TI application note here:
http://www.ti.com/tool/TIDA-00069
I'm just changing the LEDs to confirm the HSDC Pro is doing what it is supposed to be doing. The pin assignments should be correct, as they are unchanged directly from TI's code. As the pins are either tied directly to VCC or GND, the LEDs should light up (or not for the 1'b0 ones) whether or not the rest of the system is functioning as normal. What could be causing HSDC Pro to not be properly burning the firmware?
