sprintf issue - missing syscalls

[Tectu]

Hey there,

I get some problems using sprintf() because of missing syscalls:

Code: Select all

Linking build/vitfit.elf
/home/tectu/projects/resources/arm-toolchain/bin/../lib/gcc/arm-none-eabi/4.6.2/../../../../arm-none-eabi/lib/armv7-m/libc.a(lib_a-abort.o): In function `abort':
abort.c:(.text.abort+0xa): undefined reference to `_exit'
/home/tectu/projects/resources/arm-toolchain/bin/../lib/gcc/arm-none-eabi/4.6.2/../../../../arm-none-eabi/lib/armv7-m/libc.a(lib_a-signalr.o): In function `_kill_r':
signalr.c:(.text._kill_r+0xe): undefined reference to `_kill'
/home/tectu/projects/resources/arm-toolchain/bin/../lib/gcc/arm-none-eabi/4.6.2/../../../../arm-none-eabi/lib/armv7-m/libc.a(lib_a-signalr.o): In function `_getpid_r':
signalr.c:(.text._getpid_r+0x0): undefined reference to `_getpid'
collect2: ld returned 1 exit status
make: *** [build/vitfit.elf] Error 1


I found syscalls like _write, _sbrk, _read etc. with google, but none of these.

Does anyone "use successfully sprintf() with chibios?"

Also, is there a reason why these syscalls aren't in chibios/various/syscalls.c ?

[utzig]

Basically the reason is that ChibiOS is not a Unix clone. It's an RTOS made to run on constrained hardware. Also there's no kernel/userspace separation and there's no libc library.

If you are in the mood you could easily do your own sprintf using os/various/chprintf.c. Change the prototype from:

void chprintf(BaseSequentialStream *chp, const char *fmt, ...)

to

void chsprintf(char *str, const char *fmt, ...)

and everytime you have a call to _putc change it to use str. For example change:

_putc(chp, (uint8_t)c);

to

*str++ = (uint8_t)c;

This should basically do the trick.

Fabio Utzig

[mabl]

Alternatively you could also just fill the stubs. I've never run in trouble with these:

https://github.com/mabl/ChibiOS-Infrast ... bs/stubs.c

[Tectu]

Thanks for the stubs, mabl. They do indeed work without any problems.

I've one more, related question: I read everywhere, also in the ChibiOS wiki, that functions like sprintf() etc. do take a huge amount of memory. But when I create the workspace for a thread which uses sprintf(), how do I terminate the size of it?
I once read in the wiki about "finding it out" by just moving it from a big value down, until it dosen't work anymore. But isn't there any more "proper" way to do that?

[mabl]

I've one more, related question: I read everywhere, also in the ChibiOS wiki, that functions like sprintf() etc. do take a huge amount of memory. But when I create the workspace for a thread which uses sprintf(), how do I terminate the size of it?
I once read in the wiki about "finding it out" by just moving it from a big value down, until it dosen't work anymore. But isn't there any more "proper" way to do that?

There is the option to initialize the stack space full with 0x55 which is overwritten when the stack is used. The eclipse plugin supports measuring the used space that way. Of cause you have to take care that you hit all possible code path before this value is correct.

[hazelnusse]

mabl,
It looks like you removed that repository from your github -- do you have these function stubs elsewhere?

Thanks,
Luke

[mabl]

Yeah, always meant to clean it up and put it back up somwhen in the future... I am not at my development machine now - I've posted earlier versions of the stubs in the other threads.

[Tectu]

Hey there,

Here are the files you need (attachment below).


~ Tectu