Forum Discussion
New ContributorDon't find the software for MAX V CPLD Development kit
Yes, that is what I would expect to see.
You should be able to assign the board test image POF file to the FPGA, and then click the VERIFY button to check if it is preprogrammed.
The image should verify 100% if the chip is preprogrammed.
Would also verify that your board is basically functional and can be used.
Regular ContributorYes you need the USB Blaster driver installed. This board has an embedded USB Blaster implementation (pretty much all these Altera development boards do) so you need to connect it to your CPU via USB to be able to communicate with the board.
You could try launching the Quartus Programmer tool in Quartus Prime Lite and see if it detects the embedded USB blaster.
It should. Then you should be able to select that USB Blaster device, and do a scan and your MaxV device should show up in JTAG.
If you can't get the above working then either your USB blaster driver did not install correctly or your development board is misconfigured.
Since I don't have one of these boards I can't really say anything more detailed.
Typically these boards come pre-programmed with the POF (compiled binary program file) for the demo sample application.
As to why the BoardTestApplication.exe appears to do nothing I suspect is it has issues finding your embedded USB Blaster device.
As to the utility of the board, you don't really need to have the BoardTestApplication to use it, it is just a nicety when you first power on.
The other files installed by the software have the definitions of the chip top in verilog and vhdl that you would use to build your own design.
duodiscus92Quartus Prime Programmer shows as on the screenshot below.
So it seems to prove that the development kit is recognized ... isn't it ?
- duodiscus92
Curiously, Prime Programmer autodetects a 5M240Z ship but actually the board is equipped with a 5M570Z ...
- ak6dn
Not uncommon, unfortunately. The two devices happen to have the exact same 32b JTAG ID code of 0x020A60DD
From the "Max V Device Handbook v1.1" table 6-3 32b IDCODE values for the Max V.
Turns out the 5M240Z in the T144 package has the same IDCODE value as the 5M570Z in any package.
Autodetect is ambiguous in this case, and it just chose a part.
When you assign a POF file to that device, you can chose the correct part number to assign as well (ie, a manual override).
- ak6dn
Yes, that is what I would expect to see.
You should be able to assign the board test image POF file to the FPGA, and then click the VERIFY button to check if it is preprogrammed.
The image should verify 100% if the chip is preprogrammed.
Would also verify that your board is basically functional and can be used.
