Actions
Forum Thread Details
  • Replies 1 reply
  • Subscribers 300 subscribers
  • Views 565 views
  • Users 0 members are here
Related
See a helpful answer?

Be sure to click 'more' and select 'suggest as answer'!

If you're the thread creator, be sure to click 'more' then 'Verify as Answer'!

External input and output files for my MACHXO3D board

androo

Hi! 

I am currently working on a school project that requires me to implement VHDL code on a LCMXO3D-9400HC-5BG256C breakout board. My issue is that I find it difficult to "fetch" my binary input (of around 40 bits) from an external file to place it in my board, process it, and then place the output in another external file. I learned that the TEXTIO package is generally not possible during Synthesis. Initially, I saved it in a text file, but after reading about IP cores, I learned that it should be stored in a mem file. Can you help me with a step-by-step walkthrough (if possible) how I can implement this on my board?

I am relatively new to the Lattice Diamond software and MACHXO family boards, which is why I decided to ask here and am hoping for a reply.

Parents

  • I'm puzzled - why do you want to put text from a file into a physical (synthesised) design ?

    If you are simulating there are many solutions, if you are are testing a physical design there are others.

    It will help a lot if you describe your project a bit more and also the workflow.

    most people go a bit like this:

    specification/concept

    diagrams/flowcharts/pseudo-code/notes

    VHDL code

    VHDL test harness (makes the inputs and checks the outputs)

    Simulation (simulator will provide tools for making inputs and looking at outputs)

    Synthesis

    Hardware test (needs physical inputs and makes physical outputs,  eg signal generators and logic analysers)

    What does your workflow look like.

    MK

Reply

  • I'm puzzled - why do you want to put text from a file into a physical (synthesised) design ?

    If you are simulating there are many solutions, if you are are testing a physical design there are others.

    It will help a lot if you describe your project a bit more and also the workflow.

    most people go a bit like this:

    specification/concept

    diagrams/flowcharts/pseudo-code/notes

    VHDL code

    VHDL test harness (makes the inputs and checks the outputs)

    Simulation (simulator will provide tools for making inputs and looking at outputs)

    Synthesis

    Hardware test (needs physical inputs and makes physical outputs,  eg signal generators and logic analysers)

    What does your workflow look like.

    MK

Children
No Data