ghdl simulation failure

[stnolting]

ghdl simulation failure

[stnolting]

A stack overflow error in GHDL can occur if you are running out of memory due to too many simulated signals. GHDL uses several bytes for each signal and you might get problems when simulating large memories. There are simulation-optimized versions of the IMEM and DMEM components, that use constants/variables instead of the 'signals' for the memory array: sim/rtl_modules

The default testbench features a simulated UART receiver. Eachprintable char that is received from the processor's UART will be printed to the console and also written to neorv32.testbench_uart.out.

If the UART is in simulation mode (setting bit 12 in the UART control register), the actual UART transmitter logic will be disabled. All data written to the UART's TX data register will be "printed" using VHDL text.io (which is way faster than using the testbench simulated UART receiver):

• The printable ASCII char will be printed to the console and also to neorv32.testbench_uart.out.
• The full 32-bit word written to the UART'S TX data register will be printed as hex word to neorv32.uart.sim_mode.data.out.

You can automatically activate the simulation mode by using USER_FLAGS+=-DUART_SIM_MODE when compiling your applications.

[stnolting]

Is your simulation now working as expected? 🤔

[salmansheikh]

You can close this. I haven't been able to run it yet. I was thinking more of getting the Xilin Arty or Terasic DE0 board from work to put the SOC on them and take it for a whirl. Salman

…

On Thu, Jan 21, 2021 at 12:00 PM Stephan ***@***.***> wrote: Is your simulation now working as expected? 🤔 — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#5 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAZFYMHDREAMO3L73L2NQT3S3BMURANCNFSM4V53YDBA> .

-- Even a Smile is charity :) - Prophet Muhammad

[stnolting]

I'm also working with Arty and E0-nano. So if you need any help, feel free to get in contact again. 😉