tech2020

Hi elodg, Thanks for your reply. Are the steps you are referring to as shown in the screenshot ? ie: just editting the xilisf.c file to incl the Macronix part ? I found that doc rather overwhelming (.... in fact, I dont know how I managed to develop code for CMOD A7 and Vivado 2016, 5 years ago, in the first place !) What I ended up doing is as follows below...in case it helps some other newbie: *************************************************************************** I installed Vivado 2019.1 (no update), webpack w free license....on a new WIN10 machine...so totally clean install...got the free license. I then copied only the CMOD-A7 board files from the Digilent github, as documented, and placed the CMOD-A7 folder into my ...XILINX/..../boardfiles/ folder...so that Vivado has CMOD-A7 board knowledge. I copied my original 2016 project folder to a new c:/ ... folder, opened Vivado 2019.1, and open that old project..which worked fine. Ran Synthesis, Implementation, Bitstream, opened HW Mgr, connected CMOD device, Open Target, ...all worked fine, until Add Config Memory Device. Moment of truth.... Macronix, 32Mb, mx25L3233... device was present in the list of memories...which was not the case with 2016. So that is what I needed. So its programmed, and device worked as expected after removal and testing. So, prob'ly all thats required to resolve this issue for users is to inform Vivado about the new Macronix device...however, there may be non-power users like me that struggle to follow the steps provided so far. It would be great (actually, essential...) if Digilent had a doc that showed , step by step, how to inform Vivado of this new memory device...so they can keep using their existing setup..instead of doing a total new install as I did.

Hi John, Thanks for your prompt reply. Appreciate your dedication. As mentioned, I am not skilled in working with bootloader,etc and its been 5 years since I did development on this device...and I just want to program my device like before and be done with it...so production can make units. I have had success since posting as follows...for others who may have same issue: I installed Vivado 2019.1 (no update), webpack w free license....on a new WIN10 machine...so totally clean install...got the free license. I then copied only the CMOD-A7 board files from the Digilent github, as documented, and placed the CMOD-A7 folder into my ...XILINX/..../boardfiles/ folder...so that Vivado has CMOD-A7 board knowledge. I copied my original 2016 project folder to a new c:/ ... folder, opened Vivado 2019.1, and open that old project..which worked fine. Ran Synthesis, Implementation, Bitstream, opened HW Mgr, connected CMOD device, Open Target, ...all worked fine, until Add Config Memory Device. Moment of truth.... Macronix, 32Mb, mx25L3233... device was present in the list of memories...which was not the case with 2016. So that is what I needed. So its programmed, and device worked as expected after removal and testing. So, prob'ly all thats required to resolve this issue for users is to inform Vivado about the new Macronix device...however, there may be non-power users like me that struggle to follow the steps provided so far. It would be great (actually, essential...) if Digilent had a doc that showed , step by step, how to inform Vivado of this new memory device...so they can keep using their existing setup..instead of doing a total new install as I did.

I have just asked this exact same question elsewhere on the forum...as I just purchased another 5 CMOD A7, and discovered this issue, after wasting days wondering what is wrong. It is now 6 months since this original post...is there a comprehensive solution from Digilent to this production problem they introduced without notice to users ? A step by step guide would be appreciated, as popping in code snippets and forking from github is beyond my capabiilties, though I was able to get the part working with Vivado 2016.2 until this latest batch of CMODs. Perhaps there are many other users who can handle writing verilog code and using constraints files, to get working products, but that is the extent of their capabilities, and who need to continue using this part ?

Hi, Ive been using CMOD A7 for yeares w Vivado 2016.2 and Micron config flash. now the flash memory has changed to Macronix and Vivado doesnt suport it. In the CMOD-A7 Reference Manual it mentions how to resolve this...using Bootloader BSP. However I do not understand this process ?..having only ever gone down the Vivado path. Is there some more info to clarify this process ? Ultimately, all I want is for my Vivado 'configure memory device' to recognise the new Macronix memory. I am a simple GUI user, not TCL etc. Any hints appreciated, as I have several devices waiting to be programmed for prod.