-
Re: QEMU only works for one build
The same setup on my Windows box is ok. i.e. I don't see the above symptom.
I wonder if there is something screwed up in my Eclipse workspace? I might try creating a new workspace on macos, create a new blinky project, and see what happens.
-
Re: QEMU only works for one build
I tried on my mac and 3 qemu debug session in a row were ok.
first check if qemu is closed successfuly, or hangs and the next session is affected.
then install a new eclipse, somewhere in a temporary folder, (unpacked from the epp archive), create a fresh workspace and a new blinky app.
-
Re: QEMU only works for one build
I started a new workspace, created a new Blinky, clean, build, etc => problem still exists.
I deleted my Eclipse install, reinstalled Eclipse and all my plugins, opened the new workspace, clean, build, etc => problem still exists.
I rebooted the computer (hadn't been rebooted for quite some time), opened the new workspace, clean, build, etc => PROBLEM SOLVED !!
Seems as though something got screwed up in my OS .... sigh ....
-
-
Re: QEMU only works for one build
btw, I don't know if you noticed, but the graphical buttons in qemu are... live.
if your application is prepared for this, try them. I remember one of the F4DISCO templates generates code to use the user button, but I'm not sure which one.
if not, at least the reset button can be tested.
-
Re: QEMU only works for one build
Yes I had noticed. The app I'm using lights up the green LED when the user button is pressed. This also works in QEMU
The issue I'm working on at the moment is the blue LED which is asserted during the TIM10 interrupt handler. I can't get that handler to fire, so need to delve into how QEMU handles interrupts, and whether the code in `tim10.c` is fully implemented or not. There is a bit of code there and some of it is "hash-if-zeroed" out.
-
-
-
-
-