Forum Replies Created
You seem to have access to just the BSP level. If you don’t see the file usbh_hcd_rx600.c then you need to verify that you own a license for uC/USB-Host.
The following USB interrupts get enabled in USBH_RX600_Start() in usbh_hcd_rx600.c:
INTENB0 = VBSE | RSME | BEMPE | BRDYE; INTENB1 = OVRCRE | BCHGE | ATTCHE | SIGNE | SACKE;
This forum is for uC/ products. For Silicon Labs related questions please use the following one instead: https://www.silabs.com/community/mcu/32-bit/forum
Are you sure the name of the function is Clk_GetNbrDayInMonth()? I looked at version 3.09.03 and couldn’t find that function.
Try this version of the port to see if it fixes it.
The link to the release notes has been added to the actual doc pages for uC/HTTPc and uC/HTTPs as well.
You can get to the release notes from here: https://www.micrium.com/support/versions/
Apparently what that example does is just simulate data from a sensor and not exercise any type of interrupts that you would use in an RTOS-based application. With that being said, unfortunately, I have to say that we currently don’t have an example that uses I2C (properly) with Micrium OS.
I have informed our team of this situation so that in the future we can provide more meaningful examples.
It’s odd that they have sent you back here, this forum is supposed to be for non-silicon labs hardware customers.
Anyways, I will help you with your inquiry.
Your best option would be to check the example called “soc-thermometer-rtos” which is part of the Bluetooth SDK. The example comes with Micrium OS, the temperature sensor (I2C), BLE, and the mobile app.
Is that the same example project you are using as a reference? What is your version of the SDK?
Also, what is the exact part number that you are using? I know the example “soc-thermometer-rtos” works on both the EFR32BG13 and EFR32MG13.
I believe you should post this on https://www.silabs.com/communityMay 30, 2018 at 09:53 in reply to: how to support the fine resolution for STM32 + UCOSII #23998
The finest resolution you’ll get with uCOS-II is milliseconds. For nanoseconds, you will have to resort to a hardware timer.April 26, 2018 at 11:13 in reply to: uc/os-ii version for safety application，IEC61508 SIL3 #23554
Our kernels do meet with IEC 61508 Levels 1 to 3. For more information please visit our Safety Critical page here: https://www.micrium.com/certification/why-safety-critical-certification/
We don’t have any API or Shell command to check which tasks are running. However, task information and other run-time statistics are available in the form of Global Variables.
We have a PDF that describes all the variables that we use to display our Kernel Awareness screen in uC/Probe.
You can download the PDF following this link: https://www.dropbox.com/s/s3two8iy9etdp4c/uCOS-II-KA.pdf?dl=0
JanosJanuary 29, 2018 at 15:29 in reply to: μC/TCP-IP on FRDM K64F (Freescale K64F120) problem #22823
The library was generated for IAR. You would need a KDS compatible library or just switch to IAR.
JanosOctober 16, 2017 at 16:13 in reply to: uC/Probe limit access to memory and block editing mode #21907
Sorry for the late response. The two features you mentioned are being currently being developed.
Yes, in fact, the classic products have been available to customers for much longer than Micrium OS.