On 2017-08-29 15:50, marko kiiskila wrote:
On Aug 28, 2017, at 11:49 PM, [email protected] wrote:
On 2017-08-28 17:41, marko kiiskila wrote:
I just tried it, it worked for me at least.
Take a look at output from ‘newt target dep <yourtarget>’, make sure
you
seen console/full, as well as shell as listed packages.
Make sure that main() goes and executes
os_eventq_run(os_eventq_dflt_get()) in
a loop, as that’s needed for shell to pick up uart input.
On Aug 27, 2017, at 9:24 PM, [email protected] wrote:
On 2017-08-25 17:21, Christopher Collins wrote:
On Fri, Aug 25, 2017 at 09:53:26AM -0700, marko kiiskila wrote:
Also note that blinky does not have shell compiled in. It’s a very
simple
app which just blinks an LED. Try the app slinky instead; that one
has shell
enabled.
I believe Jyothi is following this tutorial which adds console and
shell
to blinky:
https://mynewt.apache.org/latest/os/tutorials/blinky_console/.
Chris
Hi chris,
Yes chris I am following that tutorial only. But not able to succeed
any one has tried for arduino M0 pro for console and shell.
Hi marko,
Thqs for your reply.
I already implemented all the packages and able to see console/full
and shell. And even I checked in main() which has
os_eventq_run(os_eventq_dflt_get()) in while loop.
In serial port setup tutorial is it must to connect to board FT232H to
arduino M0 pro to get the shell commands in console using minicom.
I am connecting programming port of arduino M0 pro to my ubuntu system
didn't connect FT232H board and can able to see the blink on the board
but unable to get the shell console.
https://mynewt.apache.org/latest/os/get_started/serial_access/
<https://mynewt.apache.org/latest/os/get_started/serial_access/>
The tutorial expects you to use the UART pins from pin header (labeled
RX<-0 and TX>-1).
Are you using those?
Tutorial also calls out minicom as the terminal program, which enables
hardware flow control
by default. Remember to turn that off.
Hi Marko,
Thanks for your help. After disabling hardware flow control in minicom
we are getting garble messages. We used minicom at 115200 bauds(the auto
baud rate is also same). One more thing, we cant see any shell prompt as
mentioned in tutorial.
