0b28232f72
* [efm32] Assume Device Identification (DI) version 1 if we don't know the OUI Silabs are using some additional OUIs we don't know about. Reported in issue #389 These should use a DI version 1 layout, so assume version 1 layout for OUIs we don't know. However do print a notice about this on DEBUG() as suggested by @UweBonnes The IDCODE value is sufficient to make a positive identification of an EFM32 device. See AN0062 Section 2.2. Therefore accepting any OUI is reasonable behaviour. Additionally the part familiy is checked, and the target rejected if not in the `efm32_devices` table. This commit makes that rejection explicit, although it does not change the logical behaviour here. Note that the important registers (part number, part family, flash size) are at the same addresses in both layouts anyhow. Currently only `efm32_cmd_serial` and `efm32_cmd_efm_info` functions use registers that differ between DI versions. * [efm32] tidy format warning about portability UB * [efm32] Simplify OUI checking * Only read the OUI once * Accept the device even if the OU is unknown, as silabs have been using a variety of OUIs * Perform fewer register reads before checking the device family is valid
Black Magic Probe
Firmware for the Black Magic Debug Probe.
The Black Magic Probe is a modern, in-application debugging tool for embedded microprocessors. It allows you see what is going on 'inside' an application running on an embedded microprocessor while it executes. It is able to control and examine the state of the target microprocessor using a JTAG or Serial Wire Debugging (SWD) port and on-chip debug logic provided by the microprocessor. The probe connects to a host computer using a standard USB interface. The user is able to control exactly what happens using the GNU source level debugging software, GDB.
See online documentation at https://github.com/blacksphere/blackmagic/wiki
Binaries from the latest automated build are at http://builds.blacksphere.co.nz/blackmagic