Hello everyone,

     I am working with c8051f340 mcu on usb device project. when I am debugging my device  using si labs ide(adapter) sometimes I had removed  my usb in middle or after running program and when plugging it in it shows "the device is malfunctioned" I had realised that the reboot is not happening correctly due to the program is running from middle way when usb plugged in...so, descriptor transfers are not happening. I tried to use vbus interrupt ISR for  restarting device...but it is not going well

   I want my device to reboot and enumerate again whenever usb plug out and plug in...even when it is debugging. can anyone help me what to do,please

Hi, I have just purchased a bunch of EFM8BB1 SOIC16 packages. The first thing I did is solder one onto a PCB with regulated +/- 3.3V on pins 4,5 along with a 1000uF 16V capacitor next to the pins for decoupling (I have also tried the full operating voltage range from 2.2V to 3.6V, and so far I have tried two physical ICs. I have also tried the addition of a 0.1uF ceramic in parallel with the bulk decoupling, but it doesn't help my problem below). Here is my schematic, my PCB wiring matches it:

Note: I have left it out for now, but I do have a pull-up resistor on pin 6 (active low reset).

Next, I have written code to toggle a pin using the blank C project in Simplicity IDE. My main code is below, and SILABS_STARTUP.A51 is untouched from default:

#include <SI_EFM8BB1_Register_Enums.h>                // SFR declarations

void SiLabs_Startup (void)
{
    WDTCN = 0xDE;           // Disable watchdog timer
    WDTCN = 0xAD;

}

SI_INTERRUPT(TIMER0_ISR, TIMER0_IRQn) {
	P0 ^= (1<<0);
}

int main (void)
{
	CLKSEL |= (0x7 << 4);
	XBR2 |= (1<<6);
	IE_EA = 1;
	IE_ET0 = 1;
	CKCON0 |= (1<<1);
	TMOD |= (1<<1);
	TCON_TR0 = 1;


  while (1) {}                             // Spin forever
}

I have also tried many combinations of ports and simpler code to initialize the pin either on or off, but my problem remains the same: the pins never change their output. The pins are typically always high. Depending on the port, I can get the pins to be always low if I use external pull-down resistors. My code seems to be not run no matter what I do, I cannot toggle pins using either push-pull, or default/floating config.

My regret here is using a third party flash programmer (owSilProg on an Arduino Uno) which is known to work, but doesn't support the C2 debug interface, so I can't debug what is happening with the program counter.

Is there anything I might be doing wrong? I need a checklist to run through to narrow down why this problem might be occuring.

 

One thing I noticed: legacy programs flash the entire .hex file no worries, but when targeting my exact 8-bit chip, the new project version for Simplicity generates what looks more like a 32-bit .hex file - it includes an extended linear address line at the start :020000040000FA which isn't accepted by interface, and this line is skipped. However, the subsequent code lines are still written to location 0x0000 (0x0000:0x0000 high and low locations doesn't make any sense for this chip??). Have been unable to fix this problem, and have been ignoring it until now. Regardless, whether I use both old (converted, without the .A51 file) and brand new project formats, my code doesn't seem to affect the IC pins (code doesn't run?)

 

EDIT: Here's my code for a "minimum failing example" with a pull-up resistor on the reset line. I'm pushing P0.0 low, but it reads +3.3V:

#include <SI_EFM8BB1_Register_Enums.h>

void SiLabs_Startup (void)
{
    WDTCN = 0xDE;           // Disable watchdog timer
    WDTCN = 0xAD;
}

int main (void)
{
	P0MDIN = 1;
	P0MDOUT = 1;
	P0_B0 = 0;

	while (1) {}            // Spin forever
}

 

A simple question I think. Have need to use built-in comparators on a new project.

The input range is given as -0.25V to VDD+0.25V. In many uses of opamp and comparator devices there are clamping diodes at the inputs which enforce these limits. Protection is provided with input resistors to limit the current to safe values while the diodes do the clamping.

I have looked in both datasheet and reference manual for information about whether the internal comparators have clamping diodes that set these limits or if they are really hard limits such that, if the input exceeds them, the comparators and possibly other built-in devices will fail to operate properly.

In this use case the voltage that needs to be compared is multiple times the max and min and, for various reasons, cannot really easily be divided down before being delivered to the comparator. Thus, if the comparators don't have clamping diodes or there are other ill effects of exceeding the range, then I'll have to use external devices. Etc.

Thanks for any help.

I am using the RTC in an ordinary way.  I have it interrupting every second to maintain a time of day clock.  I had 2 issues that I think I have now figured out, but I spent a lot of time doing so.  Perhaps documentation could be improved in these areas. Or maybe there is some, but I couldn't find it.

1) The documentation says that because of how the alarm triggers, the alarm register should be one less than the desired count.  To me that means if I have a 32768 Hz clock, I should set the alarm to 32767 to get an interrupt once a second.  Not so!  It seems the correct number is 32766 (2 less than the desired count).

2) The documentation says that the interrupt will stay true for a clock cycle, so the ISR should disable the interrupt and enable it after the interrupt has gone away.  Great!! I did that, but found that once in a while, I would miss an RTC alarm interrupt completely.  What I finally figured out is that if the RTC Alarm interrupt cannot vector while the request is true, it won't trigger at all.  I was running the CPU at 5 Mhz to save power and that meant that I my timer 2 ISR could run longer than the RTC interrupt signal was asserted. Once I figured that out, there are several abvious workarounds.  I am now running the RTC alarm interrupt at a higher priority than the timer 2 ISR and it all works fine.

Please confirm that my findings are correct, or give me the correct answers.  Please improve the documentation.

Thanks

Hi,

I have been working with the EFMSB1_SleepMode_smaRTClockWake example. I have worked out how to set the RTC alarm value in the configurator and have been playing with various options.

I need to be able to set the alarm value from code. I don't need to do it often and I could stop and reset the clock when a new alarm value is programmed. Is this possible? If so, how would i do it?

Thanks in advance,

Rob

Hi

In one of my application I'm using C8051F410 uC.

I want to monitor voltage of RTC Battery( Typical 3V) Vrtc-backup pin. I have no IO left to read this voltage through ADC.

I tried monitoring VREGEN bit in RTC0ADR, to check if  Vrtc-backup > VDD(2.5V).

Description of VREGEN says

" This bit is automatically set to 1b when Vrtc-backup > VDD "

In init, 

RTC0ADR=0x06; 

When Vrtc-backup voltage 3V, I found VREGEN bit  as 0b 

When I made Vrtc-backup voltage 1.5V, I found VREGEN bit still 0b.

I changed init to RTC0ADR=0x26;  

When Vrtc-backup voltage 3V, I found VREGEN bit  as 1b 

When I made Vrtc-backup voltage 1.5V, I found VREGEN bit still 1b.

I do not found any change in VREGEN bit when Vrtc-backup changes.

Is it possible to monitor Vrtc-backup using VREGEN???

If yes, please guide me what I am missing / doing wrong here.

Thanks

Yatin

 

Hi,

  What IDE is suggested to develop C8051F380 related product? Thanks.

Hi all,

I need the driver of C8051F340 for Win8 64 Bit(USB_Bulk)

Br

Boone

Hi,

I've been reading this forum and found plenty of good information. Maybe someone can help me. I was prototyping something on arduino and now chooose efm8ub1 for final ic in the product. I need to have ability to dive 2-3 ssd1306 oled screens. All same size, displaying same thing. 

Are there libraries available somaplce? I searched around, attempting to port from Adafruit, but Im not a good programmer. 

Any suggestions greatly appreciarted. 

 

Hi,

I have now the problem, that in the IDE the debug window  for disassembly view and watch list do not open. Other windows like the registers open normally . I tried the latest version 5.5 but that did not solved the problem.  Im a bit confused because I am working for years with this great tool and never had this problem ?? Does somebody has an answer ?

regards Karl

Is there a software available for this? Including hardware schematics, if possible? I have efm8ub2, but I guess it should work for any efm8 using SPI?

Dear Silabs-Engineer,

 

I tested AN142 FFT example linked from "https://www.silabs.com/documents/public/example-code/an142sw.zip"  (FYI, I found this link from forum-thread-title "AN142: FTT Routines for the C8051F12x Family")

Anyway I think I also have same problem like following forum thread " https://www.silabs.com/community/mcu/8-bit/forum.topic.html/an142_fft_routinesf-f5iA"

 

I hope you check this and reply soon.

Thanks in advance 

Best Regards,

Tommy Lim

Hello,

I am not able to use the DAC1 of the EFM8LB1 in Alternate mode. The trigger source CLU1 is passing a 16bit PWM from PCA. The PWM signal is present at CLU1 output - I verified it at port pin. The DAC does not update with this settings but if I change the trigger source to SYSCLK than the DAC is working. However I need to increase the resolution of the output so I have to make use of this "PWM trick" mentioned in the reference manual. A example which make use of this feature could help too.

For example, the DAC0 and DAC1 data registers may be written with adjacent
digital values, and an 8-bit PWM signal from PCA0 may be routed through a Configurable Logic unit to serve as the trigger source for
DAC1. With this configuration, the DAC1 output voltage will assume an average value representing an interpolation between the two
adjacent digital values, thus extending the resolution of the DAC to a theoretical 20 bits.

By the way there is a bug in the code generator of Simplicity Studio 4. The 16Bit PWM setting does not set the PWM bit.

I hope anyone can help me with this problem.

Best regards,

Maximilian