So in my attempt to get semihosting working I think I need to understand how
Riot and newlib currently work together. Does Riot use pre-compiled newlib
libraries? If so, where are they and how are they currently linked?
It seems I'll probably need to disable the newlib syscalls defined with
UART_STDIO etc. Not sure if there is a good way of doing this from the upper
level Makefile? Anyone know?
[photo]
Anthony Merlino
CTO & Co-founder, Verge Aero
(609)-319-1399 [tel:(609)-319-1399]
On 1/21/2017 4:13:22 PM, Anthony Merlino <anth...@vergeaero.com> wrote:
Working through all of it now. There seems to be some good info here:
http://www.wolinlabs.com/blog/stm32f4.semihosting.html
I'll post here if I get it working and maybe we can eventually add support for
this in Riot if it works out.
[photo]
Anthony Merlino
CTO & Co-founder, Verge Aero
(609)-319-1399 [tel:(609)-319-1399]
On 1/21/2017 4:11:23 PM, DipSwitch <dipswi...@ownage4u.nl> wrote:
Do you use as linker arguments --specs=rdimon.specs -lrdimon ? If not you could
give that a try.
On Jan 21, 2017 21:59, "Anthony Merlino" <anth...@vergeaero.com
[mailto:anth...@vergeaero.com]> wrote:
That makes since, I misunderstood before, I thought this was a JTAG specific
functionality. Thanks for the clarification. Unfortunately I have an external
ST-Link V2, not the onboard.
I suppose that brings the original question back. Trying to get semihosting
working. It sounds very similar to Segger RTT so it seems possible. Even better
is it shouldn't be more than an openocd command and a couple tool-chain flags
(in theory). but I'm not so sure of where to start.
[photo]
Anthony Merlino
CTO & Co-founder, Verge Aero
(609)-319-1399 [tel:(609)-319-1399]
On 1/21/2017 3:43:43 PM, DipSwitch <dipswi...@ownage4u.nl
[mailto:dipswi...@ownage4u.nl]> wrote:
Segger RTT only works with segger J-link. However if your st link came from a
nucleo or discovery you can update the firmware to a J-Link with limited
functionality.
On Jan 21, 2017 21:36, "Anthony Merlino" <anth...@vergeaero.com
[mailto:anth...@vergeaero.com]> wrote:
Thanks everyone for the suggestions. Segger RTT looks like it could be the
perfect solution. It actually sounds very similar to semihosting.
I am trying to use this with an ST-Link V2 and STM32 cortex m3 processor. Does
anyone know if it has been tested on this? I've added the module, but it
doesn't seem to be working. I have used the debug target to start gdb and my
program.
Thanks again,
Anthony
[photo]
Anthony Merlino
CTO & Co-founder, Verge Aero
(609)-319-1399 [tel:(609)-319-1399]
On 1/21/2017 2:35:16 PM, Michael Andersen <mich...@steelcode.com
[mailto:mich...@steelcode.com]> wrote:
More details in the rtt_stdio readme
https://github.com/RIOT-OS/RIOT/blob/master/sys/rtt_stdio/README.md
[https://github.com/RIOT-OS/RIOT/blob/master/sys/rtt_stdio/README.md]
On Jan 21, 2017 11:32 AM, "Michael Andersen" <mich...@steelcode.com
[mailto:mich...@steelcode.com]> wrote:
Hey, I use Segger RTT. I believe my changes were merged in to RIOT as rttstdio.
You get very high performance studio without a UART. It should be as simple as
adding the module to your makefile.
On Jan 21, 2017 10:41 AM, "Anthony Merlino" <ant.merl...@gmail.com
[mailto:ant.merl...@gmail.com]> wrote:
Hi everyone,
Has anyone used semihosting with an ARM core to allow them to use the debugger
for stdio for the shell? I don't have an available UART on this board I'm
developing for. My two options are USB or semihosting with the debugger. As USB
currently is unsupported with Riot, it'd be great to figure out how to utilize
semihosting in the meantime.
Any info is appreciated.
Sincerely,
Anthony
_______________________________________________
devel mailing list
devel@riot-os.org [mailto:devel@riot-os.org]
https://lists.riot-os.org/mailman/listinfo/devel
[https://lists.riot-os.org/mailman/listinfo/devel]
_______________________________________________ devel mailing list
devel@riot-os.org [mailto:devel@riot-os.org]
https://lists.riot-os.org/mailman/listinfo/devel
[https://lists.riot-os.org/mailman/listinfo/devel]
_______________________________________________
devel mailing list
devel@riot-os.org [mailto:devel@riot-os.org]
https://lists.riot-os.org/mailman/listinfo/devel
[https://lists.riot-os.org/mailman/listinfo/devel]
_______________________________________________ devel mailing list
devel@riot-os.org [mailto:devel@riot-os.org]
https://lists.riot-os.org/mailman/listinfo/devel
[https://lists.riot-os.org/mailman/listinfo/devel]
_______________________________________________
devel mailing list
devel@riot-os.org [mailto:devel@riot-os.org]
https://lists.riot-os.org/mailman/listinfo/devel
[https://lists.riot-os.org/mailman/listinfo/devel]
_______________________________________________ devel mailing list
devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
