Jump to content
  • 0

NOEL-ARTYA7 Programming and Debugging with GRMON


ciaociao

Question

Hello Expert,

I followed the NOEL-ARTYA7-EX Quick Start Guide (link) and met a problem at step 3.6 (Programming the bitstream).

The toolchains I'm using:

  • Ubuntu 20.04 (standalone, not WSL version or in a virtual box)
  • Digilent Arty A7 FPGA Development Board (A7-100T version)
  • Xilinx Vivado 2019.1 to program the FPGA
  • GRMON 3.2.18 64-bit eval version

1289101648_Screenshotfrom2022-11-1710-56-35.png.af676a82261ee638b4fa404d8bbcda5b.png

The bitstream was found in the Link. There is NOEL-ARTYA7 FPGA configuration files at the bottom. Since there's no EX1 processor, I chose the MC64-SC and downloaded the bitstreams to the target board. Then the HARDWARE MANAGER in vivado should be closed.

1435364979_Screenshotfrom2022-11-1711-03-02.thumb.png.9dc70b44381b486a12168155b542882c.png

Now the target board should have the NOEL-ARTY SOC (correct me pls if I'm wrong.). I continue to debug the target board with the GRMON. I chosed the uart debug link. And the port should be ttyUSB1 bucause all other ports (ttyS0-9) give me Input or Output error. But it has no access to the target board.

1773566871_Screenshotfrom2022-11-1711-08-47.png.bad26487e4d6e6d12875709b31523752.png

I also tried the digilent debug link, which needs the specific digilent adept runtime drive. But it gave me the following errors. Does this debug link method need a specific digilent HS1/HS2/HS3/SMT2/SMT3 cables? I used just a normal type A to type B cable XDDDD.

333764_Screenshotfrom2022-11-1711-13-42.png.43e08b174c531727974a535e52d4e07e.png

What should I do to go further with this GRMON debug tool? Or is the bitstream actually not the right one?

Link to comment
Share on other sites

1 answer to this question

Recommended Posts

  • 0

Hi @ciaociao,

Based on your screenshots, it looks like the board was successfully configured, but the connection between the PC and the GRMON hardware debugger isn't being established correctly. I'm not familiar with the methodology you're using here, but a Digilent JTAG module should not be needed for this - the documents linked indicate that the Arty's onboard JTAG programming circuitry is being used.

I would recommend reaching out to Gaisler for further information on how to use this debugging method.

Thanks,

Arthur

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...