Skip to content

Version 1.2.0

Choose a tag to compare

View all tags
@mubes mubes released this 05 Sep 22:05
· 50 commits to main since this release
v1.2.0
4d11770

This is the third production release of ORBTrace Mini gateware.

This build is recommended for all users. SWO capture over a UART link at up to 62Mbps has been added and an edge case in parallel TRACE addressed. No issues or regressions are foreseen.

New Features

  • SWO capture over a UART encoded link at speeds from 125Kbps to 62Mbps. Note that with SWO/UART your reception rate (as set by the -a xxxx option to orbtrace) must match the rate your target is sending data at. The effective maximum user data rate of a SWO/UART link is almost exactly the same as a SWO/MANCH link (6.2MBytes/s vs 5.8 Mbytes/s) and in general SWO/MANCH is preferred if available because it autobauds...unfortunately some chips don't offer the choice.

Note that you'll need an updated Orbuculum suite to access the new features, you can find that here. Production support for SWO/UART will be incorporated into orbuculum 2.1.0.

Bugfixes and Itchfixes

  • Prevent parallel trace keepalive from potentially corrupting a data frame.
  • Add DeviceInterfaceGUID to USB descriptors to play more nicely with Windows.
  • Various small internal improvements (See git log) with no user visible behaviour change.

Assets

Gateware set consists of the bootloader and application images. Bootloader targets dfu slot 2, application slot 1. Under normal conditions you will only need the application gateware, although updating the bootloader is needed if you want to benefit from the faster boot and improved USB compatibility.

Installation

To install you will need to have established permissions for the device (See the README, or just grab a suitable udev rules file, like this one, then hold down the button and power up the ORBTrace Mini. The status LED will turn purple. Then, in a terminal window, enter;

dfu-util -d 1209:3442 -a 1 -D orbtrace_mini_application_1.2.0.bit

Once it has flashed power cycle and you should be running the new version. You can verify that you are running the correct version by checking the interface strings;

$ lsusb -d 1209:3443 -v | grep iInterface
      iInterface              0 
      iInterface              0 
      iInterface              4 Trace
      iInterface              5 Control Proxy
      iInterface              6 CMSIS-DAP v1
      iInterface              7 CMSIS-DAP v2
      iInterface              8 Target power
      iInterface              9 Version: v1.2.0-0-g4d11770

It is also worth updating your bootloader. To do that, go into bootloader mode again and load the bootloader into slot 2;

dfu-util -d 1209:3442 -a 2 -D orbtrace_mini_bootloader_1.2.0.bit

If you goof this up you'll have to reprogram using the JTAG header and following the instructions here. Be particularly careful not to flash the application gateware into the bootloader slot. If you do that your ORBTrace will work perfectly, but you'll lose the ability to dfu-update.

Help Requested

Please test on a wide variety of targets as possible and report observed issues...ARM CORTEX-M is a broad church and wide testing is essential. Success reports are as important as failure ones, so feel free to raise an issue or ping us in the Discord.

Contributions to both ORBTrace and Orbmortem always gratefully accepted.

Upcoming Work Items

  • Documented interface to the CPU
  • any needed bugfixes :-)

Known Issues

No known issues at this time.

Assets 5
Loading