No worries, Koen. I see you've been busy elsewhere in the tree. Congrats
on the recent merges. Below are my thoughts on priorities, but of course
the implementation emerges from everyone's priorities.
Any CoAP implementation needs to include the base spec, and the Observe
and Block extensions.
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
U
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)-
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" wrote:
> That makes since, I misunderstood before, I thought this was a JTAG
> specific functionality. Thanks for the clarification. Unfortunately I
> have
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
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" wrote:
> Thanks everyone for the suggestions. Segger RTT looks like it could be
> the
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
More details in the rtt_stdio readme
https://github.com/RIOT-OS/RIOT/blob/master/sys/rtt_stdio/README.md
On Jan 21, 2017 11:32 AM, "Michael Andersen" 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
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" wrote:
> Hi everyone,
>
> Has anyone used semihosting wit
On 21 Jan 2017, at 19:40, Anthony Merlino wrote:
>
> I don't have an available UART on this board
Hi,
I’m not sure I completely understand your question, but I have a question on my
own:
We wrote the slipmux spec
https://tools.ietf.org/html/draft-bormann-t2trg-slipmux-00
so we can do diag
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 g
Hi Ken,
Sorry for the slow response. Time limitations are also an issue for me.
I'm going to look at the code in the next few weeks when I have time.
Besides the work for coap observe, what would be the priority to work on?
Koen
On 01/10/2017 12:31 PM, Ken Bannister wrote:
>
> Hi Koen,
>
> Than
12 matches
Mail list logo
