I have discovered that it seems r0 is always set to 1, meaning INIT2 is never skipped.
Good day guys, this code here is part of the initialization code for a firmware of an STM32F030 microcontroller, disassembled using Radare2. It is executed after the clock initialization but before the heap setup.
I have discovered that it seems
r0
is always set to 1, meaning INIT2
is never skipped.
What am I missing?
@Middleware & OS3 Replies
What are you trying to do
From there we would know if u re Missing something
Well, I am just trying to understand the control flow and conditions under which
INIT2
is called.