Skip to content

v0.12.0

Choose a tag to compare

View all tags
@flit flit released this 12 Sep 19:48
v0.12.0
59bb653
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

New features

  • Added thread awareness support for the RTX5 RTOS, available as CMSIS-RTOS2 and used in Mbed OS.
  • ELF file support.
    • You can now load ELF files into target flash using pyocd-flashtool.
    • Two new commands were added to pyocd-tool: where and symbol.
    • pyocd-gdbserver and pyocd-tool have a --elf command line option now.
    • Sets the stage for many future features.

Boards and targets

  • Added NXP FRDM-KW36 (kw36z4)
  • Added ST STM32F412xE (stm32f412xe) and STM32F412xG targets (stm32f412xg), plus three modules (on the Module Test Board):
    • MXChip EMW3166 (stm32f412xg)
    • Advantech WISE-1530 (stm32f412xg)
    • USI WM-BN-BM-22 (stm32f412xg)
  • Corrected problems with the TI CC3220SF reset sequence.
  • Improvement to NXP Kinetis connect logic. This fixes rare incorrect detection of a device as secured, which usually happens on specific devices that seem to have slightly different timing of flash controller initialization.

Fixes and changes

  • pyOCD will retry reading the DP IDCODE register if the first read fails, as recommended in the Arm documentation. It's possible the DP is in a state where it sees the SWJ sequence as an invalid transfer.
  • Major refactoring of connect and initialization sequence.
  • Cleanup of RTOS support log messages.
  • Made GDB server checksum calculation code compatible with Python 3.4.
  • Fixes examples in README to be compatible with Python 3.
  • Corrected trove classifiers in setup.py to list supported Python versions.
  • Fixed support for installing from GitHub archives. Starting with this version, you can download the .zip or .tar.gz from the release on GitHub and successfully run setup.py from the extraction.

Testing

  • Added makefiles to analyzer and gdb_test_program under the src/ directory.
  • The functional tests write a JUnit-style test report XML file.
  • Functional tests can be run in parallel using the --jobs option on automated_test.py. There are still occasional occurrences on Windows and Linux of a failure to open a device, so this is not yet being used in CI.
Assets 2
Loading