USB GetDeviceDescriptor causes NMI (Parity Check)

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
filkra
Posts: 15
Joined: Sat Nov 04, 2017 10:53 am

Re: USB GetDeviceDescriptor causes NMI (Parity Check)

Post by filkra »

BenLunt wrote:Yes, if the controller says it is 64-bit, you have to write zeros to the high dword of the addresses, however, only once if you wish.
It works... Turns out the host controller read the first bytes of the next qTD and interpreted them as Extended Buffer Pointers. Therefore it tried to write to an invalid address. I just added some padding to the qTD struct and everything works as expected #-o
BenLunt wrote:If this fixes your issue, plug the finger-print reader back in and see if your can still read the descriptor (of the thumb drive). I bet so.
I will try it now :)

//EDIT

After attaching the fingerprint sensor again it's still working :)
User avatar
BenLunt
Member
Member
Posts: 941
Joined: Sat Nov 22, 2014 6:33 pm
Location: USA
Contact:

Re: USB GetDeviceDescriptor causes NMI (Parity Check)

Post by BenLunt »

filkra wrote:After attaching the fingerprint sensor again it's still working :)
Good. Most of the time it is the simplest thing. Something we fail to look at because it is so simple.

Ben
http://www.fysnet.net/the_universal_serial_bus.htm
Post Reply