Marius Muench

To find the right information and changes for the SoC, you would usually iteratively reverse engineer the firmware and run it in firmwire, to see where it gets stuck; needs...

Hi @docfate111, Sorry for the delay! Usually, you would determine the addresses of peripherals via reverse engineering. You will want to add a separate class, yes. I started working on...

Hey @Br4v3H3r0, I would usually follow one of the following ways: 1) Run firmwire with debugging flags enabled, especially the ones revolving on unassigned MMIO addresses 2) Take a firmware...

Hi. When starting firmwire with --console, it usually enoughs to run `jupyter console --existing`. You are hinting towards an error message encountered during firmwire startup, but without additional logs/infos, it's...

Hi, This issue flew under my radar, sorry for the late response. To support a new SOC, you will need to provide an according loader backend for the SOC. Check...

Hi, The protocols are *only* shut down when going into fuzzing mode for Shannon. This is a conscious design decision for performance, the idea is that one would either: a)...

I added an additional example of binary functionality: export of csv for that specific binary (regardless whether it's a history file or a target binary). Having used polypyus from CLI...

Hi, thanks for the answer: 1) personally, from a CLI point of view, I think having unique names per binary (and history) may be more convenient. That being said, I...

I resolved potential merge conflicts; In any case, this PR by now is convuloted with multiple different features. do you want me to split this up in multiple PRs? Alternatively,...

Thanks for summarizing/listing all the points which came up in the discussion! What is the course of action here? Am I expected to implement all of those? There is still...