Ok, I got it. We moved from autotools to waf completely.
Hence I wrote my bsp extensions upon the new structure (but completely
forgot about it since I didn't touch the project for a half of a year)
Ok, thanks guys! I will try to figure out my build configuration and will
ask if something else is
On Sat, Jan 1, 2022, 4:02 PM Петр Борисенко wrote:
> Ok I see.
> The master branch is a bit ahead of my local one.
> And I really don't know what to think about these conflicts:
>
If this is applying a patch for an older version of RTEMS to the master,
the build system has changed
```
> # Confl
Ok I see.
The master branch is a bit ahead of my local one.
And I really don't know what to think about these conflicts:
```
# Conflicts:
# bsps/arm/stm32f4/headers.am
# bsps/arm/stm32f4/include/bsp/irq.h
# bsps/arm/stm32f4/start/bsp_specs
# c/src/lib/libbsp/arm/stm32f4/Makefile.am
```
Has `arm/stm
I reported this, Set fixed it, and the report was closed.
Either someone said “multilib, multilib, multilib” and it came back, Peter
needs to do a pull, or something has reverted.
https://devel.rtems.org/ticket/4504
A
> On 2022-January-01, at 13:56, Петр Борисенко wrote:
>
> I didn't print
I didn't print anything explisitly.
Here is call stack:
```
Thread #1 (Suspended : Signal : SIGINT:Interrupt)
output_char() at console-config.c:104 0x8007132
rtems_putc() at rtems_putc.c:31 0x800f038
_IO_Vprintf() at iovprintf.c:133 0x800b8b4
vprintk() at vprintk.c:31 0x8009aa0
printk() at printk.c
Assuming it is compiled correctly, printing this early should be via
printk().
Can you attach gdb and just walk through the BSP initialisation?
--joel
On Sat, Jan 1, 2022, 2:08 AM wrote:
> (sorry, I accidentally sent this to the dev list instead of users. too
> much cheer)
>
> It’s bombing in
(sorry, I accidentally sent this to the dev list instead of users. too much
cheer)
It’s bombing in printf. It’s so early that the stack hasn’t been set up yet,
and it’s found an error and it’s trying to poot a message out on the console,
which is also not set up yet.
Umm, what could be wrong?
