I had to install qemu also on my debian (MX 21) platform. For this reason I modified the README (see patch).
Further I also had to install gcc-arm-none-eabi and gdb-arm-none-eabi (of course!). The latter appeared relevant after I followed the instructions on https://github.com/embox/embox/wiki/How-to-flash-and-run-STM32-boards
, called from https://github.com/embox/embox/wiki/Nuklear
The connect to openocd needed a slight modification in the file name:
$ sudo openocd -f /usr/share/openocd/scripts/board/stm32f746g-disco.cfg
I'd suggest to write the tail in the wiki like this: /stm32<xxxx->disco(very).cfg
And instead of arm-none-eabi-gdb build/base/bin/embox I had to invoke gdb-multiarch ;-)
Hm, a few lines later I see the hint regarding this ;-). But it should apply do debian (bullseye).
As a sidenote: I personally am very happy with picocom:
picocom /dev/ttyACM0 -b 115200
Embox seems to occupy 798 kbytes (non-packed) binaries according to the following transcript:
Loading section .text, size 0x817b0 lma 0x8000000
Loading section .ARM.exidx, size 0x8 lma 0x80817b0
Loading section .rodata, size 0x3f060 lma 0x80817c0
Loading section .data, size 0x257c lma 0x80c0820
Using openocd flashing, the total size is reported as quite precisely 1 MB.
$ openocd -f interface/stlink.cfg -f target/stm32f7x.cfg -c init -c "reset halt" -c "flash write_image erase build/base/bin/embox"
Here too the suggestion: target/stm32<xxx>.cfg
Looks quite good & the display (with a simple demo showing a button and a few other basic gui-elements) pops up within just a little more than a second after powerup. Really behaves like OS-less system. No u-boot; no uClinux unpack to RAM etc. ;-)
When I return to the Nuklear page, I read that I have to run "grfx_rawfb stm32-ts". But the demo seems already running (after repower). The console shows continuing "FPS = 60" lines, without the ability to stop this e.g. using ctrl-C.
Now to PJSIP (https://github.com/embox/embox/wiki/PJSIP
It takes approx. 16 seconds after power-up until the red embox> prompt appears. Can I trace down what is going on during this time?
Is it correct that the backspace key cannot be used to correct typing errors? (but auto-completion works).
The sip application operates when I connect to any SIP phone. The continuous log reminds me of console-based linphone.
Regarding the gui-based client, I'm not understanding just well what you mean at the section "Configure and build Embox".
For qemu, both simple_pjua as well as sip_nuklear point to the same template. The same applies to the stm32f769i platform. Does it mean that both programs are compiled in those configurations?
In that case I'd suggest a change of this section, e.g. as follows:
Choose a supported platform:
* for availability of simple_pjua
> on 32F746GDISCOVERY make confload-project/pjsip/stm32f746g-discovery
* for availability of simple_pjua as well as sip_nuklear
> on qemu-system-i386 make confload-project/pjsip/x86-qemu
> on 32F769IDISCOVERY make confload-project/pjsip/stm32f769i-discovery
Note the correcton in x86-qemu (currently the web page says x86_qemu.