Musca-B1 Test Chip Board

Musca-B1 is a test chip and Platform Security Architecture (PSA) development platform for IoT subsystems. In addition to the Arm Cortex-M33 based subsystem, and reference architecture for Arm TrustZone-based systems, it has added Arm CryptoIsland and eFlash features for increased security assurance.

Key benefits include:

The development board image of the Musca-B1 test chip.

About Musca-B1

Musca-B1 makes integration of various IP and designing security into your products easier. It not only implements the recommendations of PSA, but also demonstrates Arm IP for evaluation purposes and provides a reference implementation that can be reused in SoC products.

Musca-B1 incorporates both CryptoCell and CryptoIsland, allowing SoC designers to prototype different use cases for either one to serve as a root of trust. It has embedded flash to improve security and better represent a real-world device. Using the latest flash memory controller, it utilizes the Global Flash Bus (GFB) standard.

Musca-B1 is also a software development platform. It has four times the RAM of Musca-A, allowing software developers to not be hindered by memory constraints.

Key product highlights

Musca-B1 is a test chip built from several Arm IP components, these include:

A block diagram to show Musca-B1 with a PSA ready system.

The test chip features Arm TrustZone and Arm CryptoIsland technology. It has improved integration over Musca-A and is manufactured in TSMC 40ULP with embedded flash. Musca-B1 expands upon the Arm secure foundation by building with partner IP.

  • Peripheral IP from Cadence such as QSPI, PWM, I2C or I2S
  • Power Management Unit from Dolphin Integration
  • PLL from Silicon Creations

It is designed to match the requirement of efficient IoT nodes, making it a good model for system development.

Key features

Development platform of choice for PSA

Musca-B1 test chip architecture demonstrates how to design PSA ready systems, providing a tried and tested development platform for secure IoT devices. It has been tested by the Arm software teams and the Arm partners to build software and tools around the Armv8-M architecture.

TrustZone for Armv8-M reference system

The subsystem architecture at the centre of the Musca-B1 test chip expands the Arm TrustZone isolation outside of the processor, throughout the system and is used by all the ecosystem surrounding the new Armv8-M processors.

Dynamic tuning for performance/power with the dual asymmetric Cortex-M33

The processing architecture of the subsystem at the heart of the Musca-B1 test chip ensures that processing performance is available when you need it, but saves energy when processing is not required.

Embedded security with CryptoIsland

Arm CryptoIsland brings a high level of isolation and security required for crypto services such as key handling, lifecycle management, encryption, authentication and others. For example, it can be used as a secure enclave for secure identity services such as Kigen SIM Solutions. 

Arm Community logo

Get more information on Musca-B from Arm Community

For useful resources, information, and discussion for the Musca-B development board, visit the Musca-B pages on Arm Development Platforms Community.

Get support

Community Forums

Suggested answer Cache clean of translation tables stops execution?
  • Cortex-A53
  • EL3
  • Cache coherency
  • Cache
  • Armv8-A
  • Cache Architecture
  • TrustZone
0 votes 4656 views 4 replies Latest 5 days ago by Maria F Answer this
Not answered Catching C++ Exceptions with GCC Arm None EABI
  • C++
  • GCC
  • GNU Arm
0 votes 198 views 0 replies Started 5 days ago by Thomas Willson Answer this
Not answered Compiling Arm Compute Lib for QNX OS 0 votes 179 views 0 replies Started 5 days ago by Gilboa Answer this
Answered ARM64 Linaro toochain Link error ( R_AARCH64_ADR_PREL_PG_HI21 )
  • Toolchain
0 votes 626 views 6 replies Latest 9 days ago by Kishan Patel Answer this
Suggested answer [armnn20.02] Running the NeuralNetworksTest_shared_partial case of Android nn will cause the tombstone problem. The source code path of the Android nn case is in the framework\ml\nn\runtime\test directory. Is there a solution to this problem? 0 votes 265 views 2 replies Latest 9 days ago by Ben Clark Answer this
Suggested answer Position inpdeped code for bootloader.
  • GCC
0 votes 279 views 2 replies Latest 9 days ago by Semiory Answer this
Suggested answer Cache clean of translation tables stops execution? Latest 5 days ago by Maria F 4 replies 4656 views
Not answered Catching C++ Exceptions with GCC Arm None EABI Started 5 days ago by Thomas Willson 0 replies 198 views
Not answered Compiling Arm Compute Lib for QNX OS Started 5 days ago by Gilboa 0 replies 179 views
Answered ARM64 Linaro toochain Link error ( R_AARCH64_ADR_PREL_PG_HI21 ) Latest 9 days ago by Kishan Patel 6 replies 626 views
Suggested answer [armnn20.02] Running the NeuralNetworksTest_shared_partial case of Android nn will cause the tombstone problem. The source code path of the Android nn case is in the framework\ml\nn\runtime\test directory. Is there a solution to this problem? Latest 9 days ago by Ben Clark 2 replies 265 views
Suggested answer Position inpdeped code for bootloader. Latest 9 days ago by Semiory 2 replies 279 views