Hi Silabs,

Are there any plans in the near future to release EFM8 series cpu with more than 64K of flash and with CAN interface?

Thank you.

I want to make a USB HID Keyboard device.
I have SLSTK2000A.
The USB HID keyboard sample program for this worked.

However,
I wrote it in my EFM8UB10F16G-C-QFN20.
But it did not work.

I wrote it via USB using hex2boot.exe and efm8load.

 

What is the problem?
Is it because it is not QFN 28?

Is it a special code for SLSTK2000A?

I am currently trying to enable the PCA peripheral in my chip to generate a PWM signal from a pin. I stumbled upon a page which asked a very similar question: https://www.silabs.com/community/mcu/8-bit/forum.topic.html/efm8_pwm-w2H9. However, I can't seem to recreate the same results that someone else has posted of the OP's code. I was wondering if I am not taking care of any other special registers or if there's something I completely missed. Thank you.

 

void InitPWM(void){
  SFRPAGE = 0x00; //making sure we are at the right sfr page
  XBR1 = XBR1|0x01; //enable PCA 0 Module Completely.
  XBR2 = XBR2|0x40; //Crossbar enabled
  PCA0CPL0 = 0x80; //setting the duty cycle to 50 %
  PCA0CPH0 = 0x00; //set to reset since not needed;

  PCA0CPM0 = 0b_0100_0010; //8 bit configuration
  PCA0PWM = 0b_0_0_0_00_000; //8 bit configuration

  P0SKIP = 0x03; //skip the pins 0 and 1
  P0MDIN = P0MDIN| 0x04;
  P0MDOUT =  P0MDOUT | 0x04; //push-pull at pin 2

  PCA0CN0 = 0b_01000000;//enable timer

}

I'm thinking since the crossbar is enabled, it should prioritize setting the pwm pin somewhere in port 0.  I tried saying its somewhere in P0.2

I just took possession of an EFM8 Laser Bee starter kit (SLSTK2030A) and plugged it in.  When I launched Simplicity Studio (V4. with 8051 IDE V 4.2.0, running under MacOS Mohave 10.14.2), it correctly recognized the board but couldn't find any Demos, Software Examples or Application Notes:

And when I tried to "change preferred SDK", none were available:

I'm sure this is simply a PICNIC situation ("Problem In Chair, Not In Computer"), but after futzing around with Manage SDKs and such, I turn to the community for insight.

Thanks in advance!

Hi, I bought a C8051F380DK development kit, but there isn't a CD inside. I would like to test the USB interrupt example code, but I need to run a GUI software to communicate with the evaluation board.  Could you please tell me where can I download this GUI software for USB communication? Thanks!

Can I use Simplicity studio to develop software for an NXP controller? Namely the P89C51RD2HBA ? Thank you. Francesco

Hi

I am using c8051f020 with an external watchdog/voltage monitor. The voltage monitor has a provision for having a key for manual reset. Now when the controller is working, if I press the key (for manual reset), the controller gets reset. However, if the controller is already in the reset state(not due to voltage) and then I press the key to reset it, the controller should come out of the reset state and start executing the code from the beginning. But that does not happen and the controller remains in the reset state. The watchdog timer is sending low to high pulse.

 

Can I port the code I am using with F320 family device to F381 without having to make changes? What care do I need to take to make sure the code works correctly after porting? I plan to move from F320 to F381 which are pin to pin compatible. I currently use I2C and SPI protocols on the device and some I/Os.

Is there an UART communication reference code that is available?

All of the datasheets for the older C8051Fxxx ToolStick products seem to have been developed under the old IDE, before Simplicity Studio took over the world.

However, they all talk about a separate program called "ToolStick Terminal" that you were supposed to run to see the UART output (pulled back through the ToolStick-to-USB interface).  I can't figure out anywhere to get access to this functionality in the new IDE.  The UART also doesn't show up as a Windows COM port, but I didn't expect it to because it never did before.

I'm running with Windows 10, Simplicity Studio (8051 IDE 4.2.0), a ToolStick base adaptor, and a ToolStick F990 Daughter Card, with the default demo project (F990DC_FeaturesDemo).  Is there some way to talk to the UART on the device?

Thanks,

Greg Nelson

 

Hi,

Please let me know if C8051F321 is obsolete.  If yes, please let me know if there is a drop-in replacement or similar replacement for C8051F321 from Silicon Labs or any other manufacturer.

Thanks,

Saribel

I am making a firmware for C8051F5xx series controller and do not want default Interrupt Vector generation.

To handle it in Simplicity IDE v3, I used "#pragma NOIV". This works in that IDE.

But when i migrated the firmware to Simplicity IDE v4 a warning is generated (*** WARNING L5: CODE SPACE MEMORY OVERLAP     FROM:    003BH   TO:      003DH). This leeds to the ignoring of the pragma "#pragma respecifies primary control, ignored     FROM:    003BH     TO:      003DH". This is the exact address where i want to insert my own interrupt vector.

What settings should i change in Simplicity IDE v4, to write my interrupt vectors without them being ignored by the compiler?

 

P.S: I am using Keil 8051 v9.53, 8051 SDK (v4.1.5) and Simplicity Studio Platform 4.2.0. The linker is BL51 not LX51

I'm frequently getting AD0S3C ADC flag set when input voltage is near ground in single-conversion mode.

From datasheet it is not clear what it means: "The AD0S3C flag will be set to ‘1’ if t here is a SINC3 filter clip during the conversion" - can I use conversion result or ignore it and start new conversion

PCA0 Configuration in the Simplicity Studio hardware Configurator has a serious bug, it seems.

It has to do with configuring the Capture/Compare registers. 

According to the reference manual

Important: When writing a 16-bit value to the PCA0CPn registers, the low byte should always be written first. Writing to PCA0CPLn
clears the ECOMn bit to 0; writing to PCA0CPHn sets ECOMn to 1.

However, when the Capture/Compare register value is less than 256 (0x100), the Configurator only writes to PCA0CPLn, but does not generate any writes to the PCA0CPHn! This causes the ECOMn bit to be cleared, causing the PCA peripheral not to work at all.

The problems I have noticed includes CCFn bit not being set, PWM output not working in 9-11bit modes, etc.

I hope Silabs will modify the Configurator to write to the  PCA0CPLn first, before configuring the PCA0CPMn. This would solve the issue of the ECOMn bit being cleared, as it will be overwritten by the write to PCA0CPMn.

In v4 how do I share common files across projects? I can share the h, but for some reason I am not able to set paths to also incorporate the common c files into the builds.