[
https://issues.apache.org/jira/browse/MYNEWT-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko Kiiskila updated MYNEWT-469:
----------------------------------
Affects Version/s: v1_0_0_rel
> Add a 'raw uart' mode to Console
> --------------------------------
>
> Key: MYNEWT-469
> URL: https://issues.apache.org/jira/browse/MYNEWT-469
> Project: Mynewt
> Issue Type: Wish
> Components: OS
> Affects Versions: WISHLIST, v1_0_0_rel
> Environment: all
> Reporter: Wayne Keenan
> Assignee: Marko Kiiskila
> Fix For: WISHLIST
>
>
> As Marko suggested on the dev list to my original text below, just add a
> 'raw' mode to the existing console.
> It would also be very useful to expose the console's CONSOLE_RX_BUF_SZ &
> CONSOLE_TX_BUF_SZ #defines as tweakable pkg and target config settings.
> -------------------------------
> Original text, ignore...
> I've found that (at least) the stdout, stdin and the assert facility depends
> on the console module; I think this is perhaps inverted, but obviously that
> depends on your view...
>
> I wish to use direct UART access and am using the console stub to placate the
> noble et. al dependancies. But as a result no assert messages can be output.
> I'd also like to wire up a third part library to stdout/in (however in the
> version I'm using these seem to be somewhat deserted constructs)
> I've not had a chance to look, but is there a low level UART HAL (perhaps
> with basic buffer support) that the console, stdio, assert can all depend on
> in more recent development versions of Mynewt?
> The OOTB MicroPython REPL console code really needs direct access to Serial
> TX/RX.
> Two key issues are:
> cons_tty.c 'mangles' RX data before
> stdout depends on console_write
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
