BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team @ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - ksw

Pages: [1]
1
Discussion - MCU / Re: 'USBH_HID_get_report()' timeout problem monitoring mouse activity
« on: February 09, 2022, 05:33:07 PM »
Further update: the timer A prescaler is 1000 in the example code and should be 100 for 1ms interrupts, so that mystery solved at least!
I still need to find a way round the 'USBH_HID_get_report()' timeout issue in my original post though.

2
Discussion - MCU / Re: 'USBH_HID_get_report()' timeout problem monitoring mouse activity
« on: February 09, 2022, 05:03:38 PM »
Update: I discovered the interrupt hander in the example code is running at 10ms interval rather than 1ms, which probably accounts for the timeout being 10s rather than the expected 1s. I currently don't understand why the the timer interrupts are at this rate when the setup does suggest it should be 1ms.
 
Further to a previous post, I'm still unable to view the timer registers from the Eclipse debugger, so can't verify they've been configured correctly.

3
Discussion - MCU / 'USBH_HID_get_report()' timeout problem monitoring mouse activity
« on: February 09, 2022, 11:28:03 AM »
Hi,

I'm experimenting with the 'USBH Example HID' example to acquire data from a fast mouse (1ms update rate). Does anyone know a way to read the HID reports in a non-blocking manner? In the example code, the API function 'USBH_HID_get_report()' waits until the HID has something to report, and if there's nothing (for what looks to be 10 seconds) it issues a 'USBH_ERR_TIMEOUT'. I'm unclear where this 10s interval is configured, since the underlying functions appear to define the timeout as 1000ms).

The bottom line is that I'd like to get the data from the mouse as soon as it starts generating it, but the problem with the example code is that on calling 'USBH_HID_get_report()' after a timeout it doesn't respond to mouse activity for another 10 seconds.

Keith

4
Discussion - MCU / Re: Viewing the FT90X peripheral registers in the Eclipse debugger
« on: February 04, 2022, 05:16:18 PM »
Problem solved! The base address for the registers is above the 256K shadow program RAM and the 64K data RAM, i.e. at 0x810000. A memory map diagram in the documentation would have made it obvious to a newbie like myself...

5
Discussion - MCU / Viewing the FT90X peripheral registers in the Eclipse debugger
« on: February 03, 2022, 05:19:00 PM »
Hi,

I've just started evaluating the FT900 MCU but am unfamiliar with the Eclipse toolchain. I'd like to be able to examine the peripheral register contents while debugging, but when I try and view the memory area containing the registers (base address = 0x10000) I just see 0xFFFF and the contents cannot be modified either, whereas I can examine and modify the RAM areas fine. Is it possible to view the peripheral register contents somehow?

Any suggestions would be greatly appreciated!

Pages: [1]