Fix USB Drivers using Device manager. View our post on fixing USB Driver issues in Windows 8. Go to Menu Run; Type device manager in the text box; Select Device Manager; Find Universal Serial Bus controllers and expand the list; Right-click Unknown Device; Select Properties from the context-sensitive menu; Select Drivers; Click Update Driver. ChipIdea device controller (CONFIGUSBCHIPIDEAUDC) Freescale MXS USB PHY support (CONFIGUSBMXSPHY) USB Gadget support (CONFIGUSBGADGET) These options are all enabled as built-in on the default ConnectCore 6 SBC kernel configuration file. The USB device driver provides the functionality upon which the USB gadget drivers work. From:: Greg Kroah-Hartman To:: linux-kernel-AT-vger.kernel.org, akpm-AT-linux-foundation.org, torvalds-AT-linux-foundation.org, stable.

the DAPLink software running on the USB interface chip for the micro:bit provides the drag and drop programming and debugging features that make the micro:bit so easy to use.

Target and Interface MCUs

The micro:bit presents itself as a USB disk when it is connected over USB, and can be programmed through this interface without the need to install any drivers. This makes it easier to use as a beginner. Furthermore, no matter what code you run on your micro:bit, or how you manage to crash the device, you can always still put a new program on using the USB connection.This is made possible by having a separate ‘interface chip’ or ‘interface MCU’ on the micro:bit dedicated to USB connections, programming and debugging.

Drivers Freescale Usb Devices Adapter

The Interface MCU is a Freescale KL27V2 or Freescale KL26 V1.

The chip that developers’ code runs on, and that all the peripherals are connected to is called the ‘target MCU’. See the Hardware page and the schematic for more details about how these two devices are connected.

The Target MCU is a Nordic Semiconductor nRF52833V2 or Nordic Semiconductor nRF51822V1.

The target and interface MCUs are connected by two interfaces:

• Serial Wire Debug (SWD) for programming the target MCU.

• UART for sending messages between the two devices. In practice, the UART from the target MCU is passed through directly to the PC over USB.

Reference design

On the reference design the interface circuit is clearly separated from the main micro:bit circuits so that you can do the following things:

• Build a board without the interface circuitry and use another debugger to program that over SWD.

• Build a board with just the interface circuitry and use that to flash other hardware that you have built that might be too small to contain its own interface chip.

DAPLink software

This interface chip is running software from Arm Mbed called DAPLink.

This software provides four USB endpoints that have specific purposes:

• MSC - USB mass storage device for drag-and-drop programming of the target MCU’s flash memory.

• CDC - serial pass-through from the target MCU to the PC. This is how messages get from the code you write onto the PC.

• HID - CMSIS-DAP compliant debug channel - this is useful if you want to use advanced debuggers like GDB or Keil to understand what’s happening (or not happening!) on your micro:bit.

• WebUSB - facilitates communicating with the device via a WebUSB capable browser.

The DAPLink software and interface chip are part of the Arm Mbed HDK

The micro:bit currently ships with DAPLink bootloader at version 0255 and interface at version 0255.

This table shows the device revision and which DAPLink Bootloader and interface it shipped with:

This table shows the latest DAPLink release for each board version that has been fully tested by the Foundation:

The DAPLink boot loader

It is possible to update the version of DAPLink running on your micro:bit. This is done using the DAPLink bootloader. This means that in fact, DAPLink is built twice for the micro:bit.

1. bootloader mode is used to for updating the main interface firmware. In this mode, the drive name is MAINTENANCE and hex files dropped onto the disk are written into the KL27 V2 or KL26 V1 flash. These files MUST contain an image of DAPLink or equivalent.
2. interface mode is used to target the nRF52833 V2 or nRF51822 V1. In this mode, the drive name is MICROBIT and the hex files dropped onto the micro:bit are written to the flash of the target MCU.

There are detailed instructions for how to update the firmware version on the micro:bit website.

You should never update your micro:bit with firmware from untrusted sources, as these could damage your micro:bit, or make it impossible to re-flash

Files on the MICROBIT drive

The flash file system presented on the micro:bit drive is entirely virtual. It is not backed by real memory, and this is why the drive ejects itself after new files are written. When a file is dropped onto the MICROBIT drive, instead of being written into flash memory (like a normal USB memory stick), it is streamed to the target MCU.

The following virtual files exist on the file-system:

• DETAILS.TXT: This file tells you about the build of DAPLink currently installed on the interface chip. In later versions of DAPLink it also includes more diagnostic information.

• MICROBIT.HTM: This is a link to microbit.org to help you get started.

After flashing occurs, there might also be a FAIL.TXT file, that gives a cause for failure.

The file error.c in the DAPLink source can help in diagnosing what these errors mean.

There is also a full list of micro:bit error codes in our Knowledgebase.

UART connection

Due to the number of pins on the Nordic Semiconductor chip, only the uart TX and RX lines are connected between the interface MCU and the target MCU. This means that there is no hardware flow control possible. This means that at higher serial speeds (baud rates above 9600), the micro:bit may drop characters being sent to it.

HID and CMSIS-DAP

The HID endpoint is for a CMSIS-DAP channel. This can most easily be used with pyOCD, an open source python library for programming and debugging Arm Cortex-M microcontrollers using CMSIS-DAP

WebUSB

The WebUSB API facilitates communicating with USB devices from the Browser.

Drivers Freescale USB Devices

It has been supported in DAPLink since version 0243, so if you have an older micro:bit, you will need to update the DAPLink firmware.

The API is currently available in Chrome based browsers (Android, Chrome OS, Linux, macOS and Windows) and is supported in the MakeCode Editor and the Python Editor. This enables you to flash your micro:bit straight from the browser without the need to save the .hex file first, and use serial communication between the micro:bit and the editor.

Updating the DAPLink full image

Please only use use these steps if you are familiar with USB bootloaders and command line tools. You should never need to perform these to update a micro:bit.

You can also flash a full DAPLink image to the V2 device using the KL27 internal bootloader. This will update both interface and bootloader.

You will need to register for and download the Bootloader Host Application (blhost) from NXP. IN the /bin folder you will find executables for your operating system.

Enter bootloader mode

To enter this mode we need to ground TP1 during board power up, this is the BOOTMODE pin in the KL27. To do that, connect with a wire (or something like a paper-clip) TP1 red circle) with any ground point (black square) as you insert the USB cable into the device.

Drivers Freescale Usb Devices Dongle

Bootloader CLI tool

Run the bootloader tool on your OS. These instructions relate to the CLI, but the GUI settings would be broadly similar.

Usage info:

Drivers Freescale Usb Devices Wireless Adapter

Flash KL27 bin file:

Drivers Freescale Usb Devices Pc Camera

Read KL27 flash contents into kl27_flash_dump.bin file: