Open venka66 opened 1 year ago
Hi, sorry, this issue slipped through the cracks. This looks like a logic bug in the probe subcommand, it currently it requires that we successfully probe the soc before listing the bridge interfaces supported in culvert, which wasn't what I was intending.
Ah, no, it's just the intent is poorly documented. I remember now. --list-interfaces
is listing the bridges we know the SoC supports, and it varies from SoC-to-SoC. To determine which SoC you have we need to have a functional AHB bridge to read out the SoC revision ID. From the output you've pasted it seems like we can't find a functional AHB bridge, so culvert
exits. This is probably a good state to be in from a security standpoint, but doesn't help you with successfully running the command.
I guess that turns the issue into a documentation problem, which also came up in #32
Hi,
I've encountered failure in probing the interfaces via in-band BMC from the host. Are there any pre-requisites that I may be missing before I start the probing?
[:~/culvert]# ./build/src/culvert probe --list-interfaces [] failed to initialise devmem bridge: -1 [] Failed to probe SoC revision: -19 [*] Failed to probe SoC, exiting: -19
Is there a support list I can refer to check which SOCs are supported by this utility?