- Silicon Labs Community
- Welcome and Announcements
- Silicon Labs Knowledge Base
- 8-bit MCU
- 32-bit MCU
- Bluetooth / Wi-Fi
- Other Products Category
- Optical/RH/Temp Sensor
- Other Products
- Hardware and Software Tools
- Simplicity Studio and Software
- General Discussions and Suggestions
- Chinese Forum
- Software Libraries
- Development Kits
- Reference Designs
- Third Party Tools
- White Papers
- Official Blog of Silicon Labs
- Chinese Blog
11-20-2016 10:40 AM
Trying to run an example program (tried all of them) for RAIL on BlueGecko EFR32BG(4100) board using Blue Gecko Wireless Starter Kit. No errors while generating and then compiling. But, then I am getting following error when I try to download the program.
"Can not preserve data in partially written pages without MCU information available. Use --force or --device to proceed". (see attachment)
Did anyone encountered this problem. The steps I followed are:
1.Selected the radio board 4100 in the Simplicity 4 launcher
2. Clicked new project and selected silicon labs rail framework & choose one of the sample application
3. Click generate button in "silicon labs rail framework" window
4. When done, press debug button.
Then I get the mentioned error.
Rail SDK version: 18.104.22.168
Any help much appreciated!!!
11-23-2016 12:18 AM
11-24-2016 09:29 AM
Thanks for testing at your side.
I use simplicity studio 4. Is there a version later than this?
Can this error happen due to locked debug access as in:
The error says the mcu information is not present. Use --device. Is there a way to set the mcu information using the --device flag?
Thanks & regards
11-25-2016 12:08 PM
Update. I tried to do the same with mighty gecko radio board and I was able to program it successfully.
So it definetly is the problem with efr32bg radio board.
11-27-2016 10:56 AM
The mighty gecko cannot be programmed anymore.
After programming the mighty gecko radio board (4150A) with the sample trx RAIL program, I disconnected the board, conencted it again tried to program the same sample application. Now it shows the same error (MCU information not available).
It seems like this has something to do with the flashing. Something happens after the first programming.
11-27-2016 11:46 AM
Seems like the switch to select Battery/USB/AEM on WSTK was towards Battery(and there was no battery) and that caused the issue in mighty gecko. Changing the switch to AEM solved the issue.
When I used the BlueGecko board, the switch was towards AEM, so this doesn't explain the problem with BG board. I will confirm whether the switch was towards AEM when using BG board and post it tomorrow.