Hi
having looked at the demo, wondering why the NUCLEO-L4R5ZI demo did not implement OTG test app like alot of the demos do ?
Is OTG supported on STM32L4R5ZI ?
NUCLEO-L4R5ZI OTG Support
Moderators: barthess, RoccoMarco
- Giovanni
- Site Admin
- Posts: 14535
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1097 times
- Been thanked: 934 times
- Contact:
Re: NUCLEO-L4R5ZI OTG Support
Hi,
It is supported by the demo under /testhal/STM32/multi/USB_CDC
Giovanni
It is supported by the demo under /testhal/STM32/multi/USB_CDC
Giovanni
Re: NUCLEO-L4R5ZI OTG Support
So i'm running up the
RT-STM32L4R5ZI-NUCLEO144 example
using target\stm32l4x.cfg for the ST-LINK
It runs but the debugging seems flakey, does not run and stop at main as it is setup to, it stops nvicInit() ??
RT-STM32L4R5ZI-NUCLEO144 example
using target\stm32l4x.cfg for the ST-LINK
It runs but the debugging seems flakey, does not run and stop at main as it is setup to, it stops nvicInit() ??
- Giovanni
- Site Admin
- Posts: 14535
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1097 times
- Been thanked: 934 times
- Contact:
Re: NUCLEO-L4R5ZI OTG Support
This is quite common, you may also try -Og which is specific for debug.
Giovanni
Giovanni
Re: NUCLEO-L4R5ZI OTG Support
Using /testhal/STM32/multi/USB_CDC
it seems to be working, but for some reason when the shell first start and you press CR for promt you never see the shell start info
i.e. chprintf(chp, "ChibiOS/RT Shell" SHELL_NEWLINE_STR);
it seems to be working, but for some reason when the shell first start and you press CR for promt you never see the shell start info
i.e. chprintf(chp, "ChibiOS/RT Shell" SHELL_NEWLINE_STR);
- Giovanni
- Site Admin
- Posts: 14535
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1097 times
- Been thanked: 934 times
- Contact:
Re: NUCLEO-L4R5ZI OTG Support
Hi,
It also happens withe USB driver, I think it is the host discarding incoming data if the virtual com port is not yet opened by any process. You may try putting a delay before spawning the shell and opening a terminal before the shell spawns.
Giovanni
It also happens withe USB driver, I think it is the host discarding incoming data if the virtual com port is not yet opened by any process. You may try putting a delay before spawning the shell and opening a terminal before the shell spawns.
Giovanni
Who is online
Users browsing this forum: Bing [Bot] and 7 guests