[riot-users] Stm32f4 Discovery Shell UART not working

Ludwig Ortmann ludwig.ortmann at fu-berlin.de
Thu Oct 30 22:02:04 CET 2014


Hi Pierre,

What terminal program are you using?

Cheers, Ludwig

On Thu, Oct 30, 2014 at 09:58:39PM +0100, Pierre Ficheux wrote:
> Hi,
> 
> Same for me. Additionnally, I got a problem with CR :
> 
> $ make BOARD=stm32f4discovery
> $ st-flash write bin/stm32f4discovery/hello-world.hex 0x8000000
> 
> �kernel_init(): This is RIOT! (Version: 2014.05-781-g4292)
>                                                           kernel_init(): jumping
>  into first task...
>                    Hello World!
> 
> regards
> 
> ----- Mail original -----
> > De: "Joachim" <hjbathb at yahoo.de>
> > À: "RIOT OS users list" <users at riot-os.org>
> > Envoyé: Jeudi 30 Octobre 2014 18:29:05
> > Objet: Re: [riot-users] Stm32f4 Discovery Shell UART not working
> > 
> > 
> > Hello Peter and Ludwig,
> > 
> > thanks for the quick reply and the "welcome".
> > 
> > I checked everything again and build the "shell" appl. as described
> > by Peter below. It doesn't work.
> > 
> > I'm using Linux MINT 17 as a virtual machine with Virtualbox.
> > 
> > === The compiler I use (from ppa:terry.guo/gcc-arm-embedded)
> > joachim at Mint-VirtualBox ~/Projekt/RIOT-master/tests/shell $
> > arm-none-eabi-gcc --version
> > arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 4.8.4
> > 20140725 (release)
> > [ARM/embedded-4_8-branch revision 213147]
> > Copyright (C) 2013 Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.  There
> > is NO
> > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> > PURPOSE.
> > 
> > === The terminal output after reset of the discovery board:
> > kernel_init(): This is RIOT! (Version: UNKNOWN (builddir:
> > /home/joachim/Projekt/RIOT-master))
> > kernel_init(): jumping into first task...
> > test_shell.
> > UART0 thread started.
> > uart0_init() [OK]
> > 
> > I have exchanged my RS232 level shifter. The same result. In case I
> > shortcut tx/rx on my level
> > shifter, I can see the keyboard hits on my terminal.
> > 
> > The only idea I have, my discovery is dead on that RX-pin for UART-0.
> > But honestly, I don't believe
> > that. I guess there is something else. Do you have a quick hint to
> > enable a debug print, if the RX
> > IRQ is running? Or may be you have another idea?
> > 
> > @Ludwig: At the moment there is no special project. First I like to
> > "play" a bit with RIOT-OS. I
> > ordered two "MRF24J40MA", a Microchip development board (should be
> > compatible with CC2420),
> > yesterday. I want to transfer data between two STM32F4 discovery
> > (with MRF24J40MA connected).
> > In case that is working, may be I want to buy more HW and build a
> > wireless sensor network. I'm also
> > interesting in routing and "self healing" networks. I'm very new to
> > 6loWPAN and RPL but as I
> > understood, that is possible!??
> > I have used TinyOS in the past for one project in my job. Nobody has
> > experience with wireless sensor
> > networks in my company and they choose TinyOS. I prefer RIOT-OS in
> > case that is working. :)
> > Further I like the XMC2Go (Infinion) to run RIOT-OS. I know you start
> > something for a port. ;)
> > 
> > Thank you very much.
> > 
> > greetings
> > Joachim
> > 
> > Am 30.10.2014 um 16:33 schrieb Peter Kietzmann:
> > > 
> > > Am 30.10.2014 um 16:16 schrieb Ludwig Ortmann:
> > >> Hi Joachim,
> > >>
> > >> On Thu, Oct 30, 2014 at 04:07:00PM +0100, Joachim wrote:
> > >>> my first posting :)
> > >> Welcome =)
> > > Welcome also from my part :-) ,
> > >>
> > >> Do you have any particular project you want to use RIOT in?
> > >>
> > >>> On my Stm32f4 Discovery it starts, I can see the startup messages
> > >>> after Reset. But it seems, that inputs from the Terminal are not
> > >>> working. There is no reaction on it.
> > >>>
> > >>> I found on gitgub a posting from Hauke. He had the same problem
> > >>> but later not and I do not why.
> > >>>
> > >>> May be Hauke or another one has a hint for me? I checked already
> > >>> my HW, it seems to be ok.
> > >> Might be something to do with your compiler - did you check the
> > >> wiki?
> > > 
> > > Maybe you just did not connect your tty/USB adapter correctly? If
> > > you
> > > compare [1] you can see the predefined pin mapping is: PA2 =
> > > UART_0_TX
> > > and PA3 = UART_0_RX. Also [2] may be of interest for getting
> > > started.
> > > I compiled the shell example (in RIOT/tests/shell) with
> > > gcc-arm-embedded
> > > and connected my adapter like described above. Then I used the
> > > pyterm
> > > tool (in RIOT/dist/tools/pyterm) and terminal IOs were working
> > > correctly.
> > >>
> > >> Cheers, Ludwig
> > > 
> > > Cheers,
> > > Peter
> > > 
> > > [1] https://github.com/RIOT-OS/RIOT/wiki/Board:-STM32F4discovery
> > > [2]
> > > https://github.com/RIOT-OS/RIOT/wiki/Getting-started-with-STM32F%5B0|3|4%5Ddiscovery-boards
> > >> _______________________________________________
> > >> users mailing list
> > >> users at riot-os.org
> > >> http://lists.riot-os.org/mailman/listinfo/users
> > > 
> > > _______________________________________________
> > > users mailing list
> > > users at riot-os.org
> > > http://lists.riot-os.org/mailman/listinfo/users
> > > 
> > _______________________________________________
> > users mailing list
> > users at riot-os.org
> > http://lists.riot-os.org/mailman/listinfo/users
> > 
> 
> -- 
> Pierre FICHEUX -/- CTO OW/OWI, France -\- pierre.ficheux at openwide.fr
>                                          http://ingenierie.openwide.fr
>                                          http://www.linuxembedded.fr
> I would love to change the world, but they won't give me the source code
> _______________________________________________
> users mailing list
> users at riot-os.org
> http://lists.riot-os.org/mailman/listinfo/users


More information about the users mailing list