Community news, upcoming events and general discussions
Threads: 36 Posts: 88
Get technical support from the community
Threads: 1427 Posts: 7608
Threads: 18 Posts: 64
Tell us how to make XDK better!
Threads: 36 Posts: 119
Share and discuss community member projects
Threads: 81 Posts: 350
I downloaded the VirtualXDK demo package from https://xdk.bosch-connectivity.com/demos
When trying to flash it on my XDK, that XDK hangs when rebooting in application mode (i.e red LED is ON, no console output whatsoever (USB interface doesn't even mount), and I of course can't see the VirtualXDK from my Android App). Error log (pretty unhepful I'm sure…):
INFO | Flashing file 'C:/XDK-Workbench/workspace/DVX_demoVirtualXDK/debug/DVX_demoVirtualXDK.bin'... INFO | XDK DEVICE 1: u INFO | XDK DEVICE 1: Ready INFO | Application checksum '89f9' successfully verified. INFO | Transmission successfully completed! INFO | Booting application... INFO | XDK DEVICE 1: Jumping to application
My XDK has bootloader version 0.0.9. Any idea where I should be looking?
FWIW I've successfuly tested other samples apps such as the lwm2m client, stream sensor over USB, etc.
I figured it out myself, and looks there are other applications that are impacted. Since I have a bootloader *without* FOTA (I got my XDK from Mouser, FWIW), I had to set the XDK_FOTA_ENABLED_BOOTLOADER env variable to 0 (which seems to be the case for many "basic" apps already, including the XdkApplicationTemplate, but apparently not for e.g MQTT_Paho or the VirtualXDK demo app…
yes, it is the Bootloader. I had the same problem.
Migration to new bootloader is not done for all packages yet and this is not transparent.
Hello Benjamin, Welcome to the XDK community. I am glad to hear that you figured it out and solved this issue by yourself. Additionally thanks to Stefan. Both of you correctly mentioned that this is a n issue with the new bootloader. Thank you very much for this hint. We really apologize the inconvenience and will migrate all demos instantaneously. Please do not hesitate to ask if you have further questions. Kind regards, Manuel
I assume your using the XDK without JTAG/SWD debugger (without would make your case easier :-) ).
The XDK Workbench 2.0 is considered to detect the BootLoader variant automatically via USB. But to make a "old" project aware of that detection, you must add the "XDK nature" to your project (and the Virtual XDK app is "old"). To add the XDK nature, select the project context menu in the XDK Workbench 2.0 (right mouse button over the project), select "Configure" and the "Add XDK Nature".
You can also select under menu "Windows -> Preferences -> XDK -> Build" to never create a FOTA container (which is for Bootloader 0.0.9 also a possible choice).
If your using the JTAG/SWD debugger, please ping again ;-)