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

Set up targeting idle eth cores on BH - won't enable because of hang debug #14817

Merged
merged 6 commits into from
Jan 10, 2025

Conversation

abhullar-tt
Copy link
Contributor

@abhullar-tt abhullar-tt commented Nov 6, 2024

Ticket

Closes #14653
No ticket, removing workaround required that was impacting p100 CI

What's changed

CI FW has been downgraded so this going back to original behaviour

09/01/25 This PR was updated to not enable BH eth cores because of a hang when running dispatch out of idle eth + async FD. This is being debugged separately and once it has been root-caused/worked around will enable targeting eth cores.

Checklist

Old CI when eth cores were enabled

09/01/25 CI without enabling eth cores

@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch from 3b0ff59 to 259a471 Compare November 11, 2024 20:48
@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch from 259a471 to d9c8f61 Compare November 20, 2024 16:39
@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch 2 times, most recently from 8f95992 to 5ef063a Compare November 25, 2024 03:42
@abhullar-tt abhullar-tt changed the title #0: Re-enable targeting idle eth cores after downgrading BH CI FW #0: Re-enable targeting idle eth cores on BH Nov 25, 2024
@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch 2 times, most recently from 3c8dc89 to f11c6b5 Compare November 27, 2024 02:01
@abhullar-tt abhullar-tt changed the title #0: Re-enable targeting idle eth cores on BH Re-enable targeting idle eth cores on BH Nov 27, 2024
@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch 4 times, most recently from 34fc134 to 778dc55 Compare December 3, 2024 04:21
@tenstorrent tenstorrent deleted a comment from nathan-TT Dec 4, 2024
@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch from 778dc55 to 7c23c0a Compare December 4, 2024 17:27
@@ -74,6 +74,8 @@ HalCoreInfoType create_active_eth_mem_map() {
.fw_base_addr = eth_l1_mem::address_map::FIRMWARE_BASE,
.local_init_addr = eth_l1_mem::address_map::FIRMWARE_BASE, // this will be uplifted in subsequent commits
// enabling active erisc
.fw_launch_addr = 0xFFB14008,
.fw_launch_addr_value = (uint32_t)eth_l1_mem::address_map::FIRMWARE_BASE,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

minor: wasn't clear what "fw_launch_addr_value" was in other contexts, maybe "fw_launch_jmp_insn" (yes, ties the use to the name, but I think that's ok)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm the reason I didn't add jump into the name is because we don't always write the jump instruction at this value. like this case above we just write FW base addr directly to the PC

tt_metal/llrt/blackhole/bh_hal_idle_eth.cpp Show resolved Hide resolved
@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch from 7c23c0a to 8460546 Compare December 23, 2024 19:11
github-actions[bot]

This comment was marked as outdated.

@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch 3 times, most recently from 9ade451 to de63dbe Compare December 29, 2024 03:15
Copy link
Contributor

@blozano-tt blozano-tt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@abhullar-tt abhullar-tt force-pushed the abhullar/enable-bh-eth branch from de63dbe to 34b61de Compare January 10, 2025 01:54
@abhullar-tt abhullar-tt changed the title Re-enable targeting idle eth cores on BH Set up targeting idle eth cores on BH - won't enable because of hang debug Jan 10, 2025
@@ -145,7 +145,7 @@ static void RunTest(WatcherFixture* fixture, IDevice* device) {
k_id_s = "";
}
expected = fmt::format(
"Device {} ethnet core(x={:2},y={:2}) virtual(x={:2},y={:2}): {}, X, X, X, X rmsg:* "
"Device {} ethnet core(x={:2},y={:2}) virtual(x={:2},y={:2}): {}, {}, X, X, X rmsg:* "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"ethnet" typo 😬

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw this in a couple places in debug_tools folder, I think thats the shorthand used

@abhullar-tt abhullar-tt merged commit eba0c3a into main Jan 10, 2025
298 of 299 checks passed
@abhullar-tt abhullar-tt deleted the abhullar/enable-bh-eth branch January 10, 2025 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

llrt.cpp uses ARCH_NAME specific include path for dev_msgs.h dev_mem_map.h eth_l1_address_map.h
6 participants