Arm Community
Arm Community
  • Site
  • User
  • Site
  • Search
  • User
Open Source Software and Platforms
Open Source Software and Platforms
Wiki Drag & Drop issues on Musca-A boards
  • Help
  • Jump...
  • Cancel
  • About this wiki
  • Supported platforms
  • Obtaining support
  • +Arm Reference Platforms deliverables
  • +A-class platforms
  • -M-class platforms
    • -IoT Subsystems
      • Corstone-300 Platforms
      • +Beetle development board
      • -Musca development boards
        • Musca Platforms Links & Resources
        • -Musca-A development board
          • Musca-A Links and Resources
          • Musca-A Frequently Asked Questions
          • Musca-A Power Rail Information
          • Drag & Drop issues on Musca-A boards
          • Musca-A Firmware update & QSPI / Boot recovery
          • Keil Support for Musca-A
          • +Musca-A Software Examples
        • +Musca-B1 development board
        • +Musca-S1 development board
        • Configuring S/NS Memory in an Armv8-M System
  • +R-class platforms
  • +FPGA prototyping boards
  • +Open source software

You are currently reviewing an older revision of this page.

  • History View current version

Drag & Drop issues on Musca-A boards

Some users of Musca-A development boards have experienced problems with the boards after dragging and dropping applications that use the security features.  Further drag and drop to the board would not work, and the board could become unresponsive.

The reason for this issue was that once the secure settings had been set up by the application, the DAPLink firmware was unable to access the memory system. So subsequent drag and drop would fail.

New firmware has now been released in which the DAPLink sets the reset vector to run from SRAM and then does a hard reset to stop the core setting any security features during drag and drop.

The new firmware, and instructions on how to install it, can be found on the Musca-A firmware page.