> On 9 Mar 2021, at 17:58, vincent Dupaquis
> wrote:
>
> Thanks for the responses, I'll have a check on this.
It is based on a bit old version of QEMU, but it is fully functional for the
peripherals used by the CubeMX initialisations.
I use it to run unit-tests, as semihosted
Liviu,
Thanks for the responses, I'll have a check on this.
The issue not testing with the HAL is that as most people use it, qemu
on these platforms is a bit useless for emulation.
On the other hand, it would be more on ST to invest on making those
emulations running ...
Best regards,
Alistair,
I am pretty sure that stepping-in somehow solves the issue, I did want
to see where the problem appeared and this behaviour was making it very
difficult to spot :/
Regards,
Vincent.
Le 09/03/2021 à 15:19, Alistair Francis a écrit :
On Mon, Feb 15, 2021 at 11:37 AM vincent
> On 15 Feb 2021, at 17:09, vincent Dupaquis
> wrote:
>
> ... stuck on the starting HAL_init() call.
HAL requires, amongst other things, the clock registers, since it sets the PLLs
for the desired frequencies.
xPack QEMU Arm [1] implements these registers, and is able to properly run the
On Mon, Feb 15, 2021 at 11:37 AM vincent Dupaquis
wrote:
>
> Hello,
>
> I am using qemu-system-arm with a netduino2 target, supposingly
> integrating a STM32F2xx chip.
>
> I tested using the STM HAL in order to make a simple program run,
> and I just failed to have it running
Hello,
I am using qemu-system-arm with a netduino2 target, supposingly
integrating a STM32F2xx chip.
I tested using the STM HAL in order to make a simple program run,
and I just failed to have it running correctly, it satyed stuck on the
starting HAL_init() call.
Debugging the
