Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems generating a Vivado-Block Design #133

Closed
AWenzel83 opened this issue Jul 29, 2021 · 2 comments
Closed

Problems generating a Vivado-Block Design #133

AWenzel83 opened this issue Jul 29, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@AWenzel83
Copy link
Collaborator

Hello,

after quite some time I was finally using an up to date version of this core again, and the probems with the axi4lite-System template from issue #8 are back :

  • IO_CFS_CONFIG needs a default value (like x"00000000")
  • the default values of XIRQ_TRIGGER_TYPE and XIRQ_TRIGGER_POLARITY need to be changed from a generic initialization with "others" to a fixed one like above

and btw:
when did you remove the "upload"-target from the makefile? That was quite convenient (But not as important now, with a working debugger and the possibility to upload via JTAG)

@AWenzel83 AWenzel83 changed the title Some Problems using a Vivado-Block Design Problems generating a Vivado-Block Design Jul 29, 2021
@stnolting
Copy link
Owner

Oh crap!
Seems like I keep forgetting about this Vivado issue over and over again... 🙈
Anyway, thanks for the hint! I will fix that (again).

when did you remove the "upload"-target from the makefile? That was quite convenient

The bootloader required additional checks in each "state" so that it jumps back to "get executable via UART" when a special char is received. Unfortunately, that required more program space than I thought and I would like to keep the default bootloader below 4kB. That is why this feature has been removed

However, I just noticed the raw upload script is still available: sw/image_gen/uart_upload.sh
The upload command needs to be changed from # to u and then it should still work - but only in the first 8 seconds after processor reset. I will also update that.

@stnolting stnolting added the bug Something isn't working label Jul 30, 2021
stnolting added a commit that referenced this issue Jul 30, 2021
Vivado "issue": generic defaults need a _fixed-size_ intialization value
stnolting added a commit that referenced this issue Jul 30, 2021
@stnolting
Copy link
Owner

Fixed!

Please open a new issue if you encounter further packaging problems. Hopefully, this was the last time that I forget about those fixed-size generic defaults... 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants