Hi,
Thanks for reaching out Renesas Community.
Do you want to use the printf function? If so, we need to redirect the printf function. Here is an sample project about this, you can take for reference:
7752.ek_ra2l1_redirect_printf.zip
BR,
NP_Renesas
Standard library in GCC toolchains doesn't contain system calls which possibly depend on hardware layer.Enable -specs=nosys.specs to link stub library or write stub functions by yourself.cf. https://stackoverflow.com/questions/22660011/undefined-reference-to-kill-getpid-and-sbrkhttps://sourceware.org/newlib/libc.html#SyscallsYou may see warnings building nosys library since it is stub.You should write functions if you don't want to see the warnings.
If you want to use printf you can also do this with semihosting, which is not the fastest method of printing messages.
If you use J-Link, I recommend to print messages via RTT Viewer. Almost all our examples on Github use this method.
@AZ_Renesas, incorrect, you can direct printf where ever you want using the low level write syscall of newlib. It doesn't have to be used with semihosting.
When you are going to use printf in GCC for Arm projects, you could use RTT (need J-Link) and Semihosting (not only with J-Link). And Dynamic Printf, alternatively. See the following FAQs:FAQ - e² studio printf console debugginghttps://en-support.renesas.com/knowledgeBase/16979385FAQ - Using e² studio projects with RTT Viewerhttps://en-support.renesas.com/knowledgeBase/21077330