Member | Action | Date |
---|---|---|
![]() |
Replied
to
Upload firmware image with HID and UART interface with XMODEM send command
Hi Arun, The CP2110 will not appear as a COM port to your OS. I suppose it may be possible to wrap the HID functions in such a way that it looks like a COM port, but only to the program that has access to your wrapper. If you need a COM port interface, I would check out a CP210x part, like the CP2102N. |
Mar 13 2020, 7:37 PM |
![]() |
Replied
to
Upload firmware image with HID and UART interface with XMODEM send command
I uploaded some python scripts to wrap the hid to uart and hid device dlls, which should be helpful, here: https://www.silabs.com/community/interface/forum.topic.html/how_to_load_the_windowsdllfilesincprogramon-s8lO As for the XMODEM protocol, you'll have to create that yourself, I didn't see any example of it in our test scripts. |
Mar 11 2020, 7:03 PM |
![]() |
Replied
to
program works only when debugger is connected
If your device still has the factory bootloader on it, pulling SCLK (PF0) high will cause it to enter into bootloader mode: https://www.silabs.com/documents/public/application-notes/an0003-efm32-uart-bootloader.pdf
Show more
|
Mar 11 2020, 2:03 PM |
![]() |
Updated
New 32-bit peripheral example projects on GitHub (Updated 2 March 2020) on
32-bit MCU - Microcontroller Forum
We've been working here to create a few more examples for EFM32/EFR32 devices that show basic examples of how to operate the device's peripherals. If you're familiar with our EFM8/C8051 examples, this is a similar setup. Basically, each peripheral (adc, gpio, i2c, etc) has a set of bare-bones examples that demonstrate some operation mode of the peripheral. Not all peripherals or modes are currently covered, but we will be adding more in the future. The repo can be found here: https://github.com/SiliconLabs/peripheral_examples -Brian Edit 3/12/19: We are migrating our discussion, questions, and bug reports for the 32-bit peripheral examples to the Issues section of the Github repository. This will allow us to track bugs and feature requests more easily. Edit 5/24/2019: We've added Series 2 examples, as well as cleaned up the repo structure. Edit 3/2/2020: - Add examples for EFR32xG22 Wireless SoC - Migrate AN0012 GPIO examples for series0, series1, and series2 to the peripheral_examples repo (previously not version controlled) |
Mar 11 2020, 1:54 PM |
![]() |
Replied
to
Is CPT112M gives interrupt at Proximity
Hi Madhav, I thought I had replied to this previously, but my reply doesn't seem to be here. To answer - all CPT devices with proximity detection use the same mechanism, and do not generate an interrupt on a proximity event. The reason Simplicity Studio is able to see this is that it uses the C2 debug interface on the device to read out the status of all of the sensors, including the prox sensor. It does this periodically, so it does not wait for an interrupt to occur to get the status. -Brian |
Mar 10 2020, 2:54 PM |
![]() |
Replied
to
program works only when debugger is connected
Are you going into a low energy mode (EM2/3)? Note that, when the debugger is connected, the device does not actually fully go into these modes, and instead goes into an equivalent of EM1.
Show more
|
Mar 09 2020, 2:57 PM |
![]() |
Replied
to
How to load the windows dll files in C program on windows sysems
Hi Arun, I've attached our test python scripts and other test applications for SLABHIDDevice and SLABHIDtoUART, that should help you get started. |
Mar 05 2020, 3:35 PM |
![]() |
Posted
IAR - clearing debug lock word from code - variable declaration on 32-bit Microcontroller (MCU) Knowledge Base
IAR makes it relatively easy to locate an initialized variable in flash. One use-case of this might be to set the Debug Lock Word (DLW) in the lock bits page to lock debug access to the device. To locate a variable in IAR, you can use the @ sign.
Only 'const' variables can be located and initialized however:
Finally, in order to keep variables that will otherwise be unused, they must be declared as '__root'. So, to clear the debug lock word purely with a global variable statement:
Make sure that, after flashing the device, the device is reset appropriately to engage the debug lock. To clear the debug lock word from executing code, see the following example: https://github.com/SiliconLabs/peripheral_examples/tree/master/series1/msc/debug_lock
|
Mar 03 2020, 5:02 PM |
![]() |
Replied
to
CP2614-A01-GM
Hi Vinay, CP210x drivers can be found here: https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers The CP2615 does not require a driver since it appears to the OS as a standard audio interface. |
Feb 27 2020, 3:54 PM |
![]() |
Replied
to
Is CPT112M gives interrupt at Proximity
Hi Madhav, I spoke with the developer for this part, and he mentioned that prox does not actually send an interrupt. It merely wakes the device up so that it can detect touches quicker, so the behavior you're seeing is normal. |
Feb 21 2020, 8:36 PM |