Re: [riot-devel] Cortex M33 support
Hi Juan, thanks for pointing out: I'll try and check with our contacts to NXP. Best, Thomas On 17/10/2018 14:17, Juan Ignacio Carrano wrote: Hi everyone, Is anybody working / wanting to work on Cortex M33 support? Currently there are no chips available for the general public. AFAICT Nordic and NXP are the only ones with pre-production parts. I'm trying to get samples from both. It would be great if we could have at least some basic support for when the devices reach the market. Also, if somebody has closer contact with either Nordic or NXP, it would be great. Regards, Juan Ignacio Carrano ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel -- Prof. Dr. Thomas C. Schmidt ° Hamburg University of Applied Sciences Berliner Tor 7 ° ° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany ° ° http://inet.haw-hamburg.de/members/schmidt Fon: +49-40-42875-8452 ° ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] shell and putchar
Hi Neil,
digging through old unread emails
Answering inline.
On 7/6/18 4:58 PM, Neil Jones wrote:
Hi all,
I'm working on improving IRQ support on PIC32 and I'm testing UART Rx using
the shell.
The shell uses putchar, but putchar is buffered and needs a flush, thus
when typing at the console I get no feedback until I press enter (the line
feed gets echo'd and then we get the flush).
I'm surprised other newlib implementations don't see this ?
I think most developers have their local program doing the 'echo' for
them and only sending lines by lines anyway.
So I personally do not really pay attention to this. I did not even knew
we were doing 'echo' by default…
A flush is probably needed here:
#if !defined(SHELL_NO_ECHO) || !defined(SHELL_NO_PROMPT)
#ifdef MODULE_NEWLIB
/* use local copy of putchar, as it seems to be inlined,
* enlarging code by 50% */
static void _putchar(int c) {
putchar(c);
fflush(STDOUT) <--- HERE
}
#else
#define _putchar putchar
#endif
#endif
I agree it could make sense to add it when in `echo` mode only.
putchar(c)
#ifndef SHELL_NO_ECHO
fflush(stdout);
#endif
As for the shell prompt it is already handled here
https://github.com/RIOT-OS/RIOT/blob/master/sys/shell/shell.c#L273-L280
I'm happy to do a PR for this, but this is very core functionality, I don't
want to break anything ??
But maybe other developers have more knowledge about this.
Cheers,
Gaëtan
Cheers,
Neil
___
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
Re: [riot-devel] Cortex M33 support
A crucial feature about this new arch is the availability of secure vs non-secure execution environment within the same chip. => we need to design how to leverage these 2 environments (simultaneously) with RIOT. On Wed, Oct 17, 2018 at 4:43 PM Juan Ignacio Carrano wrote: > > > On 10/17/18 4:19 PM, Alexandre Abadie wrote: > > Hi, > > > > Not M33, but Microchip is also selling an evaluation board with an M23. > > > > See > https://uk.farnell.com/microchip/dm320205/kit-eval-xplained-pro-32-bits/dp/2901261 > > > > Alex > > > > PS: I'm not working on it. > > > > Excellent. The basic CPU support for box cortex should be roughly the > same (something like "armv8_common"), am I right? > > I wonder how many of the new features are usable in RIOT. The stack > limit seems interesting. > > Regards, > > Juan. > ___ > 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
Re: [riot-devel] Cortex M33 support
On 10/17/18 4:19 PM, Alexandre Abadie wrote: Hi, Not M33, but Microchip is also selling an evaluation board with an M23. See https://uk.farnell.com/microchip/dm320205/kit-eval-xplained-pro-32-bits/dp/2901261 Alex PS: I'm not working on it. Excellent. The basic CPU support for box cortex should be roughly the same (something like "armv8_common"), am I right? I wonder how many of the new features are usable in RIOT. The stack limit seems interesting. Regards, Juan. ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Cortex M33 support
Hi, Not M33, but Microchip is also selling an evaluation board with an M23. See https://uk.farnell.com/microchip/dm320205/kit-eval-xplained-pro-32-bits/dp/2901261 Alex PS: I'm not working on it. - Le 17 Oct 18, à 14:17, Juan Ignacio Carrano j.carr...@fu-berlin.de a écrit : > Hi everyone, > > Is anybody working / wanting to work on Cortex M33 support? Currently > there are no chips available for the general public. AFAICT Nordic and > NXP are the only ones with pre-production parts. > > I'm trying to get samples from both. It would be great if we could have > at least some basic support for when the devices reach the market. > > Also, if somebody has closer contact with either Nordic or NXP, it would > be great. > > Regards, > > Juan Ignacio Carrano > > ___ > 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
[riot-devel] Cortex M33 support
Hi everyone, Is anybody working / wanting to work on Cortex M33 support? Currently there are no chips available for the general public. AFAICT Nordic and NXP are the only ones with pre-production parts. I'm trying to get samples from both. It would be great if we could have at least some basic support for when the devices reach the market. Also, if somebody has closer contact with either Nordic or NXP, it would be great. Regards, Juan Ignacio Carrano ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
