Or... Do I have to *write the data to corresponding hardware registers in the enque itself *and wait for the interrupt routine to receive the data and release the semaphore? Basically enque of Lpc17xxx (which I am using as reference) seems generic and not updating any hardware registers...
With best regards, Phani. On Tue 25 Feb, 2020, 8:35 PM Phani Kumar, <phanikumar...@gmail.com> wrote: > Hi Greg and all, > I am developing the USB Host driver for RX65N, and using lpc17xxx port as > my basic reference. Currently I can detect the device and initiate the > standard "usbhost_enumerate()" function. This calls tballoc twice and > prepares the buffer for (i) first setup packet request and (ii) for data to > be received. This results in series calls to > xxx_usbhost_ctrlin() //Think this is getting ready for reading the > returend data from device > -> xxx_usbhost_ctroltd () //This creates the Transfer Descriptror for the > data transer > -> xxx_usbhost_alloc_xfrinfo () //Prepares the data to be transmitted > (setup packet to get teh device descriptor) > -> and finally xxx_enquetd () //this prepares the pointers ready to be > transmitted > and then waits for completion on semaphore > Some how I am not able to figure out, who/how transfer the data to actual > hardware registers here? If the host keeps keeps pumping the data (with > enque), where does the deque i.e. taking this out and sending out to device > happens? > Think I am missing very basic thing. Let me know if you have any pointers/ > suggestion for me. > With best regards, > Phani. > >>