STM32L496 USB error Topic is solved
Re: STM32L496 USB error Topic is solved
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?
- Giovanni
- Site Admin
- Posts: 14457
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
Re: STM32L496 USB error
I don't know, I need to try first.
My idea is that the OTG on L4 is misbehaving for some reason, interrupts are out of logic order, maybe this is another instance of the problem fixed earlier.
Giovanni
My idea is that the OTG on L4 is misbehaving for some reason, interrupts are out of logic order, maybe this is another instance of the problem fixed earlier.
Giovanni
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:
Here its in the middle of the screenshot:
Other than that garbage, the signals looks good to me.
Cheers
Vinz
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:
Here its in the middle of the screenshot:
Other than that garbage, the signals looks good to me.
Cheers
Vinz
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.
Re: STM32L496 USB error
steved wrote: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 for the hint. At this point i don't think it is worth the effort though.
I tend to agree with Giovanni that this is probably another issue between the driver and the usb peripheral.
Once this has been verified / disproved i will do more measurements.
Cheers
Vinz
- Giovanni
- Site Admin
- Posts: 14457
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
- Giovanni
- Site Admin
- Posts: 14457
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
Who is online
Users browsing this forum: No registered users and 25 guests