Ah i see. It has been fixed in 18.2.2.
Thanks!
Search found 130 matches
- Sat Jan 19, 2019 1:16 pm
- Forum: Bug Reports
- Topic: STM32L4XX port does not handle STM32_LSCOSEL
- Replies: 3
- Views: 4427
- Tue Jan 15, 2019 10:19 pm
- Forum: Bug Reports
- Topic: STM32L4XX port does not handle STM32_LSCOSEL
- Replies: 3
- Views: 4427
STM32L4XX port does not handle STM32_LSCOSEL
Hi Giovanni,
in STM32L4xx mcuconf.h there is STM32_LSCOSEL but in hal_lld.c it is not taken into account when setting up the clocks.
Best regards
Vinz
in STM32L4xx mcuconf.h there is STM32_LSCOSEL but in hal_lld.c it is not taken into account when setting up the clocks.
Best regards
Vinz
- Fri Nov 09, 2018 10:04 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
Hi Giovanni,
I have bought a nucleo board and tried to reproduce the problem there without result.
In the end it was an issue with my hardware.
Thanks for your time!
Vinz
I have bought a nucleo board and tried to reproduce the problem there without result.
In the end it was an issue with my hardware.
Thanks for your time!
Vinz
- Sun Oct 28, 2018 1:08 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
Can I suggest you set up the scope to look at those signals in differential mode? That way you'll have a better idea of the actual logic levels seen by the CPU. It may be that the data is always one or zero; or maybe there are edges which cause the data to be misinterpreted.
Hi Steved,
thanks ...
Hi Steved,
thanks ...
- Thu Oct 18, 2018 8:39 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
Attached you will find a screenshot from sigroc logic analyzer as well as from my scope.
It looks like after the data0 of the setup there is garbage on the line.
I can't tell if this is caused by the peripheral not doing the right thing or a hardware problem.
Here its "SYNC ERR" to the right ...
It looks like after the data0 of the setup there is garbage on the line.
I can't tell if this is caused by the peripheral not doing the right thing or a hardware problem.
Here its "SYNC ERR" to the right ...
- Thu Oct 18, 2018 7:06 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
Could this also be caused by faulty hardware e.g. bad usb signalling? Does it make sense to investigate in that direction e.g. check the signals and make a trace using a usb protocol analyzer?
- Sun Oct 14, 2018 8:02 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
DOEPINT_13 seems to be "nak":
https://www.intel.com/content/www/us/en ... 93052.html
Maybe this makes sense to you.
https://www.intel.com/content/www/us/en ... 93052.html
Maybe this makes sense to you.
- Sun Oct 14, 2018 5:33 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
Trace of different error on different host port:
...
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000010 /* GINTSTS_RXFLVL ...
...
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000010 /* GINTSTS_RXFLVL ...
- Sun Oct 14, 2018 5:19 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
Trace of failure:
...
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00080000 /* GINTSTS_OEPINT */)
OEPINT(src = 0x00010000)
otg ...
...
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00000008 /* GINTSTS_SOF */)
lld_serve_interrupt(sts = 0x00080000 /* GINTSTS_OEPINT */)
OEPINT(src = 0x00010000)
otg ...
- Sat Oct 13, 2018 2:52 pm
- Forum: Bug Reports
- Topic: STM32L496 USB error
- Replies: 17
- Views: 14720
Re: STM32L496 USB error
Giovanni wrote:Could you give a try to trunk code? there is a significant difference in the OTGv1 driver.
Giovanni
Did test against trunk. Same behavior.
Vinz