Iam unable to recover from this error -> 'Could not connect debugger' while trying to debug using j-link.
The simplicity commander is unable to connect to the target with this error message -> 'Could not connect to target device'
(The blinky application is still running though) Attached are the simplicity studio logs.
Could someone please suggest a way to recover from this error. (The J-link commander also says 'cannot connect to target').
Note: I have a 10k resistor mounted between pins 2 and 10 for the purpose of making the board enter boot mode, but the board still doesn't enter the boot mode - but that would perhaps be a different issue pending to debug if iam able to recover from this current error.
We're doing development on a product that requires a third party to be able to run the flash programming utility. As part of this process, we're writing a set of instructions, including installation instructions.
One critical bit of information seems to be missing:
What are the minimum Windows requirements for the Silicon Labs Flash Programming Utility?
This source says the majority of installations of it (when the information was compiled) ran Windows 7.
This source says it runs on "Windows 2000, Windows XP, and Windows Server 2003"
AN117 says it "can be loaded by any Win32 programming environment".
How much of the above is still correct? Have the most recent versions been tested on older OS versions?
We use Simplicity Studio with 8051SDKv4.1.1.
A warning will be issued when the program is created and build.
What does this mean?
Please teach me the workarround.
I am using EFM32 Parts for my work. I am trying to build a platform so that I can generate projects from the command line and import code from the intended repositories.
I would like to integrate the entire project build into a Makefile. As the first step, I was trying to understand if I can have the entire simplicity studio process (Workspace + Project build) automated as part of a MakeFile.
I looked up the AN1121: Headless Builds with Simplicity Studio v4 note but couldnt understand whats an ISC file needed for the project generation.
In my existing projects, generated from the UI as well, I couldnt find the .isc file.
Need some help
When I follow the instructions provided here, for importing an existing project (procedure towards end of posting at following link):
no import window opens, nor does anything else happen. No message/error, nothing.
I have tried via rt-clk in Proj Explorer - select Import - MCU Project, as well as via the File - Import menu.
I am running with Simplicity V4.
I have a project created with same ver. of Simplicity on another PC, that I want to import on a different PC. That is it. Really basic. Yet the import functionality appears to be dead.
Please advise how to fix. Thank you for your time and help.
I have attached screenshot The function names are not displayed instead hex values are displayed. How can function names be displayed?
I am using SS v4 and trying to build soc-empty project for thunderboard react
I am using Gecko sdk version 2.2.2
When I try to build the project it gives error that hal-config-board missing
I'm using Visual Studio V4 to debug code on a EFM32GG11 Giant Gecko Part# SLSTK3701A. When I click on the Registers perspective I only see two groups of registers, General and FPU. I have attached a screenshot for reference. Can anyone tell me how to get all registers to appear in the Registers perspective for viewing?
I have been programming the BGM121 board using The Flash Programmer in Simplicity Studio IDE Tools option. I explored and found that the standalone Flash Programming Utility can be used for programming without the IDE. But when i launch the flash utility with BGM121 board connected, the utility doesnt recognize the board(i assume the starter kit board should be detected under USB Debug Adapter) and im unable to connect it.
Can someone help me to make this option workout?
I’m trying to debug my code throw on the EFR32MG12P433 board, compiling it with IAR 8.22.2. Searching on the forum, I found a similar problem where the program can be compiled and correctly flashed on the board, but I can’t debug the code (https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/breakpoints_not_work-rU3x ). Is there a time table on when Simplicity is going to be compatible with 8.22 version of IAR?
Thank you very much,
I am using the Simplicity Studio IDE version 4 with a C8051F340 device. When I select debug In the Run menu and then download the code to the device, I have noticed that addresses that are NOT used are not erased. Is there a means where I can change something in the configuration of the IDE so that before downloading, the entire device is erased .... or better yet, a specific range of addresses/pages ?
I realize I could write a program to alter the HEX file produced by the Keil compiler so that the entire 63 KB code space is used. Would like to try to avoid that if possible.