I'm trying to get the NXP SC16IS740 SPI UART   NXP SC16IS740 SPI UART working and am having trouble with function versus SPI Mode. I'll put more detail as needed. but my understanding(?) is that the transfer is SPI Mode 0. This is from the UART data sheet.

Looks like clock is initially low, CS* goes low, input data is sampled on the rising edge of clock.

I do this and it doesn't work. In my case below, I'm writing 0xB8 (R/W*=1, A[3:0]=7).  The first 8 clocks are a write to the UART to define the register to read back, the second 8 clocks should return the register contents (and it's not 0xFF).

SPI0CFG = 0x40;              // SFR Pages = All. Master mode enable, SPI Mode 0.  NFG

Now here I was just frustrated and playing around and I set the SPI Mode to

SPI0CFG = 0x60;   // SFR Pages = All. Master mode enable, SPI Mode 1. ~OK? last read bit floats up

Here you can see the bottom trace is now driven by the UARTand it's outputting the expected value. I don't like that the last bit (I assume) goes Hi-z which maybe is because another clock edge was expected??

This is my first SPI in a long time and normally I just bit-bang since it's only a few dozen uS anyway.  Help?  Comments? Questions? Experiences?

 

 

 

 

 

I have a EFMB883 demoboard and looks it locked the factory bootloader on the MCU (the evaluation one).

I already flash the factory bootloader and if I press pin low to enter bootloader it looks it enter, as it will do nothing, but will not respond to commands.

I tried use the SimplicityCommander but it gives an error of "layout memory" and I can't runt he unlock commands. Other commands says that are only available to EFM32.

Is there some way I can unlock and make the factory bootloader work again?

 

Hi, all.

I would like to put specific value at specific address in code segment.
I can point at specific address using "_at_".

Following is example;

uint8_t code GammaTable[10] _at_ 0x3800 =
{
    0, 1, 2, 3, 4, 5, 6, 7, 8, 9
};

But that occurs build error.
According to C51, absolute variables cannot be initialized. 
Are there any good methods for initialing to specific address in code segment?
 

(I'm a student in Japan.Sorry if my question is hard to read).

I have done crafts with toolstick in the past.

It didn't work last year and I solved it on this site's forum.

Here is the thread I referred to at the time.

https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/informational_thread-kgyL

I tried to make it work today, but Windows doesn't recognize the toolstick.

I believe the same thing is happening, but I can't find similar symptoms and can't separate out if it's an individual problem.

So I'd like to have someone who knows more about it suggest some kind of method.

What I'm using.
-ToolStick-F330DC
-PC(windows10 1909)( I'm not too familiar with it, but KB4556799 was the last base system update)
-USB extension cable in ToolStick Starter Kit (no broken wires are confirmed)

I understand that my skills are not good enough, but please help me out.

Hi All,

Today my project stopped working abruptly. I am developing for an EFM8SB2 on a custom board using the USB debug adapter. The board has an LED on pin 1.6 that is turned on during the Main startup process. There are two other LEDs connected to show I/O status and it sends diagnostic messages out its UART. One minute it was working. I changed a few lines of code and hit build and it does nothing. The LED glows faintly as if the the pin is in an intermediate state.

If I unplug the debug adapter, or disconnect pin 2.7 or RSTb, then Simplicity Studio gives predictable error messages. The debug adapter lights flash in the proper manner but nothing happens. I try to start a debug session with a breakpoint at the first operations in Main()  or SiLabs_Startup and the session starts but there is nothing happening. The step buttons and greyed out. The zombie debug session has to be terminated.

I tried with another board with exactly the same results. I tried running it on the development board, with its own built-in debug adapter and an LED connected to the same pin 1.6 and it behaved exactly the same as the custom boards. I tried an old version, configured for the dev board, and it worked properly.

The only conclusion I left is that there is a setting in the project that is causing this problem. I have spent several hours looking at settings and they all seem fine.

Any clues about this behavior would be much appreciated.

Thanks in advance,

Rob

 

After writing this I rebooted my PC and restarted Simplicity Studio. The log seems to show that the debug adapter and the MCU are working properly:

C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\usb\usb_monitor.exe C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\usb\usb_monitor.exe -d -s
C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\inspect_c8051\device8051.exe C:\SiliconLabs\SimplicityStudio\v4\developer\adapter_packs\inspect_c8051\device8051.exe -slist -sn EC3005ABDF7 -vid 4292 -pid 32836
list: 8087:0a2a@006:007[5&15A3B914&0&7] 04f3:2098@006:006[5&15A3B914&0&6] 1bcf:2b8a@006:005[5&15A3B914&0&5] 10c4:8044@006:002[EC3005ABDF7] 046d:c52b@007:004[6&36206893&0&4] 
deviceCount = 1
device (EC3005ABDF7) {
  adapterLabel = USB Debug Adapter
  SerialNo = EC3005ABDF7
  targetInterface = c2
  Name = EFM8SB20F64G-QFN24
  Type = MCU
  Family = 8051
  BoardID = 
  BoardCount = 0
  HardwareID = 0x16
  DerivativeID = 0x3
  HardwareRev = 0x6
  DerivativeRev = 0xc
  Unsupported = 0
  Indeterminate = 0
  Connected = 0
  Locked = 0
  AdapterType = EC3
}

 

Hi,

I am using C8051F502 for CAN communication. When I setup the ID# CAN0IF1A1 = 0x0001;  it works fine.

I have dip switch to setup the ID#. When I read the switch setting to a register and try give the value to CAN0IF1A1=Switch, the CAN communication do not work.

The setting of CAN registers are in SFRPAGE  = CAN0_PAGE; and my switch setting register is in Legacy SFRPAGE.

How can we change the value of CAN0IF1A1 ?

Your reply is much appreciated. Raffi

It seems it would not be difficult to get MCS BASIC 52 to run without additional external RAM on some of the Silabs parts. Has anyone ported the BASIC 52 interpreter already?

Regards,

Bert

EDIT: See additional discussion in the Studio forum thread

https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/informational_thread-kgyL

 

The latest updates to Windows 10 and Windows 7 have caused reported issues with Silicon Labs' Toolstick adapters, 8-bit debug adapters, and 32-bit debug adapters.

 

The updates in question are:

KB4487044  (Win10 ver 1809)

KB4487017 (Win10 ver 1803)

KB4486563 (Win7)

 

The reported behavior is that the debug adapters do not enumerate properly. Affected devices will not show up in the Windows Device Manager. Example bug reports are linked below.

1 2 3

 

If you are running into these issues you can try to roll back the above updates. However note that Microsoft places some restrictions on rolling back an update. For more information about rolling back a windows update and Microsoft's restrictions on uninstalling updates click the links below.

Windows Patching Information

Windows 10 Update FAQ

If you are able to roll back these updates but still experience issues, please submit a support ticket here.

 

Silicon Labs is in contact with Microsoft and we are working to resolve the issue. Updates will be posted here.

C8051f500 is used as the master device, which is connected with the slave device tle5012b (three wire, SCK, data, CS) through SPI bus (SCK, MOSI, MISO, NSS 4 wire) and communicates with it. How to design the interface and configure c8051f500?

thank you!

I developed a UART bootloader and an application for F392 with SS v4. I also have an update app that feeds a hex file to the UART bootloader over a tty. All work fine: the bootloader, the F392 app, and the update app. I can successfully flash different versions of the F392 app at will using the update app.

To get ready for low volume production I tried using the SiLabs Flash utility based on the 4.80 DLL, with USB programmer/C2. I connect to the F392 OK. When I flash the combined bootloader and app hex files, the app doesn't run. When I flash the bootloader and app hex files separately, the app doesn't run. 

What I can say:

• The F392 app hex files from SS v4 are OK since I can flash them using the update app.
• The USB programmer/C2 interface is OK since I used it with SS v4 for development.
• The F392/board is OK since I used it during development.
• I have successfully used the SiLabs flash utility in the past, but not the most recent (DLL 4.80). Any issues with 4.80 and F392?

Are the Halt and Go buttons new with the latest flash utility? On the flash utility, what is the "Text file start address (HEX)" used for? If for loading, this is available from the hex file. For execution? Doesn't it just reset the MCU when flash is complete?

Any ideas on what is going on?

Hello everyone ,i have some problem with Jovy System RE8500 BGA Rework station the pcb board from rework mashin use c8051f340 MCU for controlling processes, unfortunately  the mcu is broken ,i put new one (soldered) in order to provide  original  jovy systems-firmware  i need  to flash usb bootloder to mcu or to activate usb port in the mcu ,so i ask for clarification which file i need to flash ?there are many file in folder as200 here? thank you

I want to buy a C8051F500DK development kit, but the kit does not contain CD-ROM, and my development environment cannot be connected to the Internet. Do you have a stand-alone (non connected) software support for C8051F500DK?

If I remove the EFM8BB1 chip from an EFM8BB1LCK and replace it with an EFM8LB12F64E-C-QSOP24, will the j-link debugger recognize and work with the EFM8LB1 ??

Please note: the fancier development kits are great. I have some of those too for various of your chips. But to actually get a project going the LCK format is IDEAL! 

With the LCK I have unencumbered access to all the IO.  

If the answer is "no", I strongly encourage you to do an LCK for the Laser Bee!