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

Missing System Memory Map for Ibex Demo System #81

Open
utku1998 opened this issue Dec 19, 2023 · 1 comment
Open

Missing System Memory Map for Ibex Demo System #81

utku1998 opened this issue Dec 19, 2023 · 1 comment

Comments

@utku1998
Copy link

In the case of "Ibex Simple System (https://github.com/lowRISC/ibex/tree/master/examples/simple_system)", the memory map of the system is shown in the figure below:

image

However, I could not find a similar memory map, which shows where are the memory regions of the "Ibex Demo System" peripherals, such as GPIO, SPI, UART and also RAM etc. In the file "demo_system_regs.h", I have found the following values:

image

But is there a memory map (documentation), which shows the exact memory regions (start address, size, etc.) of the peripherals and RAM?

@marnovandermaas
Copy link
Contributor

Unfortunately, we don't have documentation for this. But we do have the software abstractions to deal with this. For example, if you want to interact with SPI you can include https://github.com/lowRISC/ibex-demo-system/blob/main/sw/c/common/spi.h
This also has the register offsets in it. However, you should not need these as you can use the functions to interact with the block:

void spi_init(spi_t *spi, spi_reg_t reg, uint32_t speed);
void spi_send_byte_blocking(spi_t *spi, char c);
spi_status_t spi_get_status(spi_t *spi);

Additionally, you can find the offsets and size of regions in the RTL: https://github.com/lowRISC/ibex-demo-system/blob/main/rtl/system/ibex_demo_system.sv#L32-L63

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