cli_test on Genesys2

[BaoBao-zhu]

Is there an existing core-v-mcu bug for this?

• [X] I have searched the existing bug issues

Bug Description

I attempted to run the application on the Genesys2 board in the quickstart folder, but the command line was unable to return to clitest. May I ask if clitest currently supports Genesys2, and how can I verify the program on Genesys2?

[MikeOpenHWGroup]

Hi @yelabWang, thanks for your interest in the CORE-V-MCU. The Quick Start Guide does not support the Genesys2 board (and I have not personally tried it). Having said, that the Makefiles do support Genesys2, but you will need to dig through the Makefiles and scripts to built and compile it all properly.

@gmartin102 are you aware of any specific documentation provided for the Genesys2 hardware?

[gmartin102]

There is no specific documentation, but it might be related to the fact that the genesys2 board runs at different clock rates from the than the Nexsys board. The CLI test code will need to be modified for the correct baud rate. How was the CLI-test program loaded into memory? Eclipse through the Ashling JTAG or a digilent HS2?

Greg

From: Mike Thompson @.> Date: Sunday, May 14, 2023 at 3:04 PM To: openhwgroup/core-v-mcu @.> Cc: Greg Martin @.>, Mention @.> Subject: Re: [openhwgroup/core-v-mcu] cli_test on Genesys2 (Issue #306) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi @yelabWanghttps://github.com/yelabWang, thanks for your interest in the CORE-V-MCU. The Quick Start Guide does not support the Genesys2 board (and I have not personally tried it). Having said, that the Makefiles do support Genesys2, but you will need to dig through the Makefiles and scripts to built and compile it all properly.

@gmartin102https://github.com/gmartin102 are you aware of any specific documentation provided for the Genesys2 hardware?

— Reply to this email directly, view it on GitHubhttps://github.com/openhwgroup/core-v-mcu/issues/306#issuecomment-1546989886, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP2QBU5HLXA4YAJRJ3TIDHTXGE3GFANCNFSM6AAAAAAYAUNLMU. You are receiving this because you were mentioned.Message ID: @.***>

[BaoBao-zhu]

There is no specific documentation, but it might be related to the fact that the genesys2 board runs at different clock rates from the than the Nexsys board. The CLI test code will need to be modified for the correct baud rate. How was the CLI-test program loaded into memory? Eclipse through the Ashling JTAG or a digilent HS2? Greg From: Mike Thompson @.> Date: Sunday, May 14, 2023 at 3:04 PM To: openhwgroup/core-v-mcu @.> Cc: Greg Martin @.>, Mention @.> Subject: Re: [openhwgroup/core-v-mcu] cli_test on Genesys2 (Issue #306) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi @yelabWanghttps://github.com/yelabWang, thanks for your interest in the CORE-V-MCU. The Quick Start Guide does not support the Genesys2 board (and I have not personally tried it). Having said, that the Makefiles do support Genesys2, but you will need to dig through the Makefiles and scripts to built and compile it all properly. @gmartin102https://github.com/gmartin102 are you aware of any specific documentation provided for the Genesys2 hardware? — Reply to this email directly, view it on GitHub<#306 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP2QBU5HLXA4YAJRJ3TIDHTXGE3GFANCNFSM6AAAAAAYAUNLMU. You are receiving this because you were mentioned.Message ID: @.***>

I tried using the uart burning program, but after modifying the baud rate and clock cycle, I still couldn't run clitest correctly