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

Porting to other MicroBlaze #4

Open
newfrogg opened this issue Aug 4, 2024 · 1 comment
Open

Porting to other MicroBlaze #4

newfrogg opened this issue Aug 4, 2024 · 1 comment

Comments

@newfrogg
Copy link

newfrogg commented Aug 4, 2024

Hi Viktor, did you porting this block design on MicroBlaze V ? I'm very curious about this.

@newfrogg newfrogg changed the title Porting to other MicroBlaze version Porting to other MicroBlaze Aug 4, 2024
@viktor-nikolov
Copy link
Owner

Hi!
No, I haven't tested this design with MicroBlaze V. At the moment, I see no benefit from using MicroBlaze V in my projects. 😃
I believe that in terms of using DDR SDRAM, the MicroBlaze Classic and MicroBlaze V should behave the same.

If you try it yourself, I would be glad to hear if it works.

When you open the HW Design published in this repository in Vivado 2024.1, it will first ask you to upgrade IPs. Then, the "Run Block Automation" will propose converting MicroBlaze Classic to MicroBlaze V.
To be on the safe side of timing, I suggest reducing the MicroBlaze frequency to 100 MHz for the first test.
Do use Vitis Classic 2024.1, not Vitis 2024.1 (i.e., Vitis Unified). Vitis Unified is an unstable mess, and it didn't support MicroBlaze when I tried it. Looking at Xilinx Forums, I'm not the only one having trouble with the MicroBlaze in Vitis Unified.

Just so you know, the testing app from this repository will not work with MicroBlaze V because it contains assembly code specific to MicroBlaze Classic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants