Skip to content

[WIP] Fix ublaze tcl to use 4MB memmap#183

Draft
activexray wants to merge 9 commits into
casper-astro:m2021afrom
activexray:m2021a
Draft

[WIP] Fix ublaze tcl to use 4MB memmap#183
activexray wants to merge 9 commits into
casper-astro:m2021afrom
activexray:m2021a

Conversation

@activexray

@activexray activexray commented Oct 19, 2022

Copy link
Copy Markdown
Contributor

Not working yet

@activexray activexray changed the title Fix ublaze tcl to use 4MB memmap [WIP] Fix ublaze tcl to use 4MB memmap Oct 19, 2022
@activexray

Copy link
Copy Markdown
Contributor Author

This did not seem to fix it

Here is some output from the toofow run, not sure if it's helpful

Slave segment '/axi_slave_wishbone_classic_master_0/S_AXI/reg0' is being assigned into address space '/microblaze_0/Data' at <0x44C0_0000 [ 4M ]>.
Slave segment '/axi_timebase_wdt_0/S_AXI/Reg' is being assigned into address space '/microblaze_0/Data' at <0x41A0_0000 [ 64K ]>.
Slave segment '/axi_timer_0/S_AXI/Reg' is being assigned into address space '/microblaze_0/Data' at <0x41C0_0000 [ 64K ]>.
Slave segment '/axi_uartlite_0/S_AXI/Reg' is being assigned into address space '/microblaze_0/Data' at <0x4060_0000 [ 64K ]>.
Slave segment '/microblaze_0_local_memory/dlmb_bram_if_cntlr/SLMB/Mem' is being assigned into address space '/microblaze_0/Data' at <0x0000_0000 [ 128K ]>.
Slave segment '/microblaze_0_local_memory/ilmb_bram_if_cntlr/SLMB/Mem' is being assigned into address space '/microblaze_0/Instruction' at <0x0000_0000 [ 128K ]>.
Slave segment '/microblaze_0_axi_intc/S_AXI/Reg' is being assigned into address space '/microblaze_0/Data' at <0x4120_0000 [ 64K ]>.
WARNING: [BD 41-2670] Found an incomplete address path from address space '/microblaze_0/Data' to master interface '/microblaze_0_axi_periph/M05_AXI'. Please either complete or remove this path to resolve.
WARNING: [BD 41-2670] Found an incomplete address path from address space '/microblaze_0/Data' to master interface '/microblaze_0_axi_periph/M06_AXI'. Please either complete or remove this path to resolve.
WARNING: [BD 5-699] No address segments matched 'get_bd_addr_segs -addressables -of_objects /microblaze_0_axi_periph/xbar/M05_AXI'
WARNING: [BD 5-699] No address segments matched 'get_bd_addr_segs -addressables -of_objects /microblaze_0_axi_periph/xbar/M06_AXI'

@jack-h

jack-h commented Nov 23, 2022

Copy link
Copy Markdown
Member

Did this get completed in the end?

@jkocz

jkocz commented Nov 23, 2022

Copy link
Copy Markdown
Contributor

@jack-h As I understand it, this is not yet ready for merge.

@kiranshila can you confirm this is still WIP / convert to draft?

@activexray activexray marked this pull request as draft November 23, 2022 18:21
@activexray

Copy link
Copy Markdown
Contributor Author

Yeah iirc I still had issues after all these changes - I was reasonably sure I needed to rebuild the JAM image but ran into too many problems even to start.

@jkocz

jkocz commented May 12, 2023

Copy link
Copy Markdown
Contributor

This should now be addressed in the m2021a-dev branch. @liuweiseu made similar changes and found it to work.

Leaving this open for the moment until we're sure all issues are addressed, but hopefully we can now close it.

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

Successfully merging this pull request may close these issues.

3 participants