Hi, stdio is on A2 and A3. See the "Connecting via Serial" section in the common Bluepill / Blackpill documentation page:
http://api.riot-os.org/group__boards__common__blxxxpill.html Kind regards, Marian On Fri, 18 Sep 2020 19:02:56 +0200 Javier Fileiv <javier.fil...@gmail.com> wrote: > Hello... :( again me... > > Even though I' ve connected a USB_UART converter to PIN A9 and A10 as it > says periph_conf.h I have no stdout output... do I need to enable anything > else? > > static const uart_conf_t uart_config[] = { > { > .dev = USART1, > .rcc_mask = RCC_APB2ENR_USART1EN, > .rx_pin = GPIO_PIN(PORT_A, 10), > .tx_pin = GPIO_PIN(PORT_A, 9), > .bus = APB2, > .irqn = USART1_IRQn, > #ifdef MODULE_PERIPH_DMA > .dma = 2, > .dma_chan = DMA_CHAN_CONFIG_UNSUPPORTED > #endif > }, > > El vie., 18 de sep. de 2020 a la(s) 18:08, Javier Fileiv ( > javier.fil...@gmail.com) escribió: > > > Hi everyone, it's me again... after a lot of digging I found the issue... > > First my OPENOCD_SCRIPTS was pointing to an OpenOCD modified for ESP32, so > > the [find xxx] command was just not doing well :( > > After, I had to set the variable STLINK_VERSION to 2 with this command line > > > > make STLINK_VERSION=2 QUIET=0 BOARD=bluepill-128kib flash > > > > And as Marian said... manual reset as STLink v2 clone doesn't do the reset > > even though the RESET pin is connected. > > > > Voila voila! > > > > Thanks again, I can keep working now! > > > > Javi > > > > El jue., 17 de sep. de 2020 a la(s) 19:44, <users-requ...@riot-os.org> > > escribió: > > > >> Send users mailing list submissions to > >> users@riot-os.org > >> > >> To subscribe or unsubscribe via the World Wide Web, visit > >> https://lists.riot-os.org/mailman/listinfo/users > >> or, via email, send a message with subject or body 'help' to > >> users-requ...@riot-os.org > >> > >> You can reach the person managing the list at > >> users-ow...@riot-os.org > >> > >> When replying, please edit your Subject line so it is more specific > >> than "Re: Contents of users digest..." > >> > >> > >> Today's Topics: > >> > >> 1. Re: users Digest, Vol 92, Issue 3 (Javier Fileiv) > >> > >> > >> ---------------------------------------------------------------------- > >> > >> Message: 1 > >> Date: Thu, 17 Sep 2020 19:43:32 +0200 > >> From: Javier Fileiv <javier.fil...@gmail.com> > >> To: users@riot-os.org > >> Subject: Re: [riot-users] users Digest, Vol 92, Issue 3 > >> Message-ID: > >> < > >> cabvwo2ds-auyetx3kbk7uomtjjvjizp6rxmpvsomrr1_60a...@mail.gmail.com> > >> Content-Type: text/plain; charset="utf-8" > >> > >> Hello everyone, it's me again... well I was able to finally build (Thanks > >> Alex). But in any case I was able to flash from Riot's make. > >> > >> I've tried as Marian said, with the reset button (even if the GPIO is > >> connected to the fake STLink) and nothing worked. Any other hint? I was > >> able, again, to flash it with st-flash > >> > >> > >> sourceCode/riot/examples/hello-world/bin/bluepill/hello-world.bin > >> arm-none-eabi-size > >> sourceCode/riot/examples/hello-world/bin/bluepill/hello-world.elf > >> text data bss dec hex filename > >> 10112 112 2372 12596 3134 > >> sourceCode/riot/examples/hello-world/bin/bluepill/hello-world.elf > >> rm -f sourceCode/riot/examples/hello-world/bin/bluepill/.test > >> sourceCode/riot/dist/tools/openocd/openocd.sh flash > >> sourceCode/riot/examples/hello-world/bin/bluepill/hello-world.elf > >> ### Flashing Target ### > >> Open On-Chip Debugger 0.10.0 > >> Licensed under GNU GPL v2 > >> For bug reports, read > >> http://openocd.org/doc/doxygen/bugs.html > >> Warn : ignoring extra IDs in hl_vid_pid (maximum is 1 pair) > >> hla_vid_pid (vid pid)* > >> > >> sourceCode/riot/examples/hello-world/../../Makefile.include:689: recipe > >> for > >> target 'flash' failed > >> make: *** [flash] Error 1 > >> make: Leaving directory 'sourceCode/riot/examples/hello-world' > >> > >> ST_Flash log > >> > >> st-flash --reset write examples/hello-world/bin/bluepill/hello-world.bin > >> 0x08000000 > >> st-flash 1.6.0-31-gf5d0454-dirty > >> 2020-09-17T19:42:12 INFO common.c: Loading device parameters.... > >> 2020-09-17T19:42:12 INFO common.c: Device connected is: F1 Medium-density > >> device, id 0x20036410 > >> 2020-09-17T19:42:12 INFO common.c: SRAM size: 0x5000 bytes (20 KiB), > >> Flash: > >> 0x10000 bytes (64 KiB) in pages of 1024 bytes > >> 2020-09-17T19:42:12 INFO common.c: Attempting to write 10224 (0x27f0) > >> bytes > >> to stm32 address: 134217728 (0x8000000) > >> Flash page at addr: 0x08002400 erased > >> 2020-09-17T19:42:12 INFO common.c: Finished erasing 10 pages of 1024 > >> (0x400) bytes > >> 2020-09-17T19:42:12 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL > >> core id > >> 2020-09-17T19:42:12 INFO flash_loader.c: Successfully loaded flash loader > >> in sram > >> 10/10 pages written > >> 2020-09-17T19:42:13 INFO common.c: Starting verification of write complete > >> 2020-09-17T19:42:13 INFO common.c: Flash written and verified! jolly good! > >> > >> > >> El lun., 14 de sep. de 2020 a la(s) 12:00, <users-requ...@riot-os.org> > >> escribi?: > >> > >> > Send users mailing list submissions to > >> > users@riot-os.org > >> > > >> > To subscribe or unsubscribe via the World Wide Web, visit > >> > https://lists.riot-os.org/mailman/listinfo/users > >> > or, via email, send a message with subject or body 'help' to > >> > users-requ...@riot-os.org > >> > > >> > You can reach the person managing the list at > >> > users-ow...@riot-os.org > >> > > >> > When replying, please edit your Subject line so it is more specific > >> > than "Re: Contents of users digest..." > >> > > >> > > >> > Today's Topics: > >> > > >> > 1. Using RIOT and bluepill (Javier Fileiv) > >> > 2. Re: Using RIOT and bluepill (Marian Buschsieweke) > >> > 3. Re: Using RIOT and bluepill (Alexandre Abadie) > >> > > >> > > >> > ---------------------------------------------------------------------- > >> > > >> > Message: 1 > >> > Date: Sun, 13 Sep 2020 22:17:27 +0200 > >> > From: Javier Fileiv <javier.fil...@gmail.com> > >> > To: users@riot-os.org > >> > Subject: [riot-users] Using RIOT and bluepill > >> > Message-ID: > >> > <CABvwO2BDBdUVWU5NMUEjfE2EeWJiqBN8u= > >> > j0hzqgem61yfe...@mail.gmail.com> > >> > Content-Type: text/plain; charset="utf-8" > >> > > >> > Hi everyone, I'm trying to implement the vl53l0x driver on RIOT. To > >> have a > >> > simple working scenario I'm trying to flash an example using stlinkV2 > >> and > >> > the bluepill (STM32F103xx) and I can't make the 'flash' and 'debug' > >> targets > >> > work. Can someone give me a hint on how to make it work? > >> > > >> > "make QUIET=0 BOARD=bluepill-128kib all" works fine. > >> > > >> > Also when wanting to blink a led, the build says... > >> > > >> > > >> .../gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: > >> > >> > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/vectors_f1.o: > >> > >> > in function `dummy_handler': > >> > ...riot/cpu/stm32/vectors/vectors_f1.c:27: multiple definition of > >> > `dummy_handler'; > >> > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/STM32F103xB.o:.../riot/cpu/stm32/vectors/STM32F103xB.c:14: > >> > >> > first defined here > >> > > >> > > >> ...gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: > >> > >> > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/vectors_f1.o:.../riot/cpu/stm32/vectors/vectors_f1.c:87: > >> > >> > multiple definition of `vector_cpu'; > >> > > >> > > >> ...riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/STM32F103xB.o:/.../riot/cpu/stm32/vectors/STM32F103xB.c:57: > >> > >> > first defined here > >> > > >> > I know my stlink works as "st-flash --reset write > >> > bin/bluepill/tests_xtimer_msg_receive_timeout.bin 0x08000000" works > >> fine. > >> > > >> > Thanks for your help! :) > >> > -------------- next part -------------- > >> > An HTML attachment was scrubbed... > >> > URL: < > >> > > >> http://lists.riot-os.org/pipermail/users/attachments/20200913/929d166d/attachment-0001.htm > >> > >> > > > >> > > >> > ------------------------------ > >> > > >> > Message: 2 > >> > Date: Sun, 13 Sep 2020 22:30:53 +0200 > >> > From: Marian Buschsieweke <marian.buschsiew...@ovgu.de> > >> > To: users@riot-os.org > >> > Subject: Re: [riot-users] Using RIOT and bluepill > >> > Message-ID: <20200913223053.1a92e079@faultier2go> > >> > Content-Type: text/plain; charset="us-ascii" > >> > > >> > Hi, > >> > > >> > did you connect the reset pin of your blue pill to the debugger? > >> Without a > >> > physical reset signal flashing won't work. For more details consult the > >> > doc [1] > >> > > >> > Also, if you happen to own a cheap ST-Link v2 clone rather than an > >> official > >> > one: I was told that the reset pin of them is often broken. You can > >> > manually > >> > press the reset button instead: Hold it down until you see the OpenOCD > >> > output > >> > and release it then. > >> > > >> > Regarding the "dummy_handler": We should rename the dummy_handler in the > >> > ISR > >> > vectors to avoid symbol name collisions like that. Feel free to open an > >> > issue > >> > to track this. For now, just rename your function, e.g. to "my_handler". > >> > > >> > Kind regards, > >> > Marian > >> > > >> > [1]: http://api.riot-os.org/group__boards__common__blxxxpill.html > >> > > >> > On Sun, 13 Sep 2020 22:17:27 +0200 > >> > Javier Fileiv <javier.fil...@gmail.com> wrote: > >> > > >> > > Hi everyone, I'm trying to implement the vl53l0x driver on RIOT. To > >> have > >> > a > >> > > simple working scenario I'm trying to flash an example using stlinkV2 > >> and > >> > > the bluepill (STM32F103xx) and I can't make the 'flash' and 'debug' > >> > targets > >> > > work. Can someone give me a hint on how to make it work? > >> > > > >> > > "make QUIET=0 BOARD=bluepill-128kib all" works fine. > >> > > > >> > > Also when wanting to blink a led, the build says... > >> > > > >> > > >> .../gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: > >> > >> > > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/vectors_f1.o: > >> > >> > > in function `dummy_handler': > >> > > ...riot/cpu/stm32/vectors/vectors_f1.c:27: multiple definition of > >> > > `dummy_handler'; > >> > > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/STM32F103xB.o:.../riot/cpu/stm32/vectors/STM32F103xB.c:14: > >> > >> > > first defined here > >> > > > >> > > >> ...gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: > >> > >> > > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/vectors_f1.o:.../riot/cpu/stm32/vectors/vectors_f1.c:87: > >> > >> > > multiple definition of `vector_cpu'; > >> > > > >> > > >> ...riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/STM32F103xB.o:/.../riot/cpu/stm32/vectors/STM32F103xB.c:57: > >> > >> > > first defined here > >> > > > >> > > I know my stlink works as "st-flash --reset write > >> > > bin/bluepill/tests_xtimer_msg_receive_timeout.bin 0x08000000" works > >> fine. > >> > > > >> > > Thanks for your help! :) > >> > > >> > -------------- next part -------------- > >> > A non-text attachment was scrubbed... > >> > Name: not available > >> > Type: application/pgp-signature > >> > Size: 228 bytes > >> > Desc: OpenPGP digital signature > >> > URL: < > >> > > >> http://lists.riot-os.org/pipermail/users/attachments/20200913/48a9a615/attachment-0001.sig > >> > >> > > > >> > > >> > ------------------------------ > >> > > >> > Message: 3 > >> > Date: Sun, 13 Sep 2020 22:49:30 +0200 (CEST) > >> > From: Alexandre Abadie <alexandre.aba...@inria.fr> > >> > To: RIOT OS users list <users@riot-os.org> > >> > Subject: Re: [riot-users] Using RIOT and bluepill > >> > Message-ID: > >> > <1548433348.3409353.1600030170970.javamail.zim...@inria.fr> > >> > Content-Type: text/plain; charset="iso-8859-1" > >> > > >> > Hi Javier, > >> > > >> > The build issue caused by the multiple definition of dummy_handler is > >> > probably due to the fact that you first build a very recent version of > >> RIOT > >> > and then went back to a branch based on an old version. > >> > The latest master contains changes in stm32 to automatically generate > >> the > >> > vectors file (here it's STM32F103xB.c). If you checkout an older > >> version, > >> > the generated file is still there because it's ignored by git. So you > >> end > >> > up with 2 files defining the same isr functions (STM32F103xB.c and > >> > vectors_f1.c) and these 2 files are automatically built by the build > >> > system. > >> > > >> > I suggest that you either remove cpu/stm32/vectors/STM32F103xB.c or > >> rebase > >> > your branch (probably the branch with your driver code?) on top of > >> latest > >> > master. > >> > > >> > Alex > >> > > >> > ----- Le 13 Sep 20, ? 22:17, Javier Fileiv <javier.fil...@gmail.com> a > >> > ?crit : > >> > > >> > > Hi everyone, I'm trying to implement the vl53l0x driver on RIOT. To > >> have > >> > a > >> > > simple working scenario I'm trying to flash an example using stlinkV2 > >> > and the > >> > > bluepill (STM32F103xx) and I can't make the 'flash' and 'debug' > >> targets > >> > work. > >> > > Can someone give me a hint on how to make it work? > >> > > >> > > "make QUIET=0 BOARD=bluepill-128kib all" works fine. > >> > > >> > > Also when wanting to blink a led, the build says... > >> > > > >> > > >> .../gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: > >> > >> > > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/vectors_f1.o: > >> > >> > > in function `dummy_handler': > >> > > ...riot/cpu/stm32/vectors/vectors_f1.c:27: multiple definition of > >> > > `dummy_handler'; > >> > > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/STM32F103xB.o:.../riot/cpu/stm32/vectors/STM32F103xB.c:14: > >> > >> > > first defined here > >> > > > >> > > >> ...gcc-arm-none-eabi-9-2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld: > >> > >> > > > >> > > >> .../riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/vectors_f1.o:.../riot/cpu/stm32/vectors/vectors_f1.c:87: > >> > >> > > multiple definition of `vector_cpu'; > >> > > > >> > > >> ...riot/examples/hello-world/bin/bluepill-128kib/stm32_vectors/STM32F103xB.o:/.../riot/cpu/stm32/vectors/STM32F103xB.c:57: > >> > >> > > first defined here > >> > > >> > > I know my stlink works as "st-flash --reset write > >> > > bin/bluepill/tests_xtimer_msg_receive_timeout.bin 0x08000000" works > >> fine. > >> > > >> > > Thanks for your help! :) > >> > > >> > > _______________________________________________ > >> > > users mailing list > >> > > users@riot-os.org > >> > > https://lists.riot-os.org/mailman/listinfo/users > >> > -------------- next part -------------- > >> > An HTML attachment was scrubbed... > >> > URL: < > >> > > >> http://lists.riot-os.org/pipermail/users/attachments/20200913/f7f4ed9e/attachment-0001.htm > >> > >> > > > >> > > >> > ------------------------------ > >> > > >> > Subject: Digest Footer > >> > > >> > _______________________________________________ > >> > users mailing list > >> > users@riot-os.org > >> > https://lists.riot-os.org/mailman/listinfo/users > >> > > >> > > >> > ------------------------------ > >> > > >> > End of users Digest, Vol 92, Issue 3 > >> > ************************************ > >> > > >> -------------- next part -------------- > >> An HTML attachment was scrubbed... > >> URL: < > >> http://lists.riot-os.org/pipermail/users/attachments/20200917/e61d2fdb/attachment.htm > >> > >> > > >> > >> ------------------------------ > >> > >> Subject: Digest Footer > >> > >> _______________________________________________ > >> users mailing list > >> users@riot-os.org > >> https://lists.riot-os.org/mailman/listinfo/users > >> > >> > >> ------------------------------ > >> > >> End of users Digest, Vol 92, Issue 6 > >> ************************************ > >> > >
pgpShFR1l8nTd.pgp
Description: OpenPGP digital signature
_______________________________________________ users mailing list users@riot-os.org https://lists.riot-os.org/mailman/listinfo/users
