pyocd / pyocd/pyOCD

pyocd pack --install stm32f767zi Does this work?

Open
#751 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1.5k
Forks
560
Avg merge
1h 41m
Merged PRs (30d)
3

Description

Wish to use:
C:\WINDOWS\system32>\python37\Scripts\pyocd pack --install stm32f767zi

Installed on Windows 10:
https://www.python.org/ftp/python/2.7.17/python-2.7.17.amd64.msi
https://www.python.org/ftp/python/3.8.0/python-3.8.0-amd64.exe
https://github.com/libusb/libusb/releases/download/v1.0.21/libusb-1.0.21.7z (\libusb-1.0.21\MS64\dll) 114KB
https://github.com/libusb/libusb/releases/download/v1.0.22/libusb-1.0.22.7z (\libusb-1.0.22.7\MS64\dll) 119KB

This Works:
pyocd list --targets --pack=C:\python37\Keil.STM32F7xx_DFP.2.12.0.pack

Using (\libusb-1.0.21\MS64\dll) 114KB [UNPLUGGED BOARD]
C:\Python37>pyocd gdbserver --pack=C:\python37\Keil.STM32F7xx_DFP.2.12.0.pack Waiting for a debug probe to be connected... [CONNECTED BOARD] 0006656:INFO:board:Target type is stm32f767zi 0006866:INFO:dap:DP IDR = 0x5ba02477 (v2 rev5) 0006941:INFO:ap:AP#0 IDR = 0x74770001 (AHB-AP var0 rev7) 0006951:INFO:rom_table:AP#0 ROM table #0 @ 0xe00fd000 (designer=020 part=451) 0006951:INFO:rom_table:[0]<e00fe000:ROM class=1 designer=43b part=4c8> 0006956:INFO:rom_table: AP#0 ROM table #1 @ 0xe00fe000 (designer=43b part=4c8) 0006961:INFO:rom_table: [0]<e00ff000:ROM class=1 designer=43b part=4c7> 0006961:INFO:rom_table: AP#0 ROM table #2 @ 0xe00ff000 (designer=43b part=4c7) 0006971:INFO:rom_table: [0]<e000e000:SCS-M4 class=14 designer=43b part=00c> 0006971:INFO:rom_table: [1]<e0001000:DWT class=14 designer=43b part=002> 0006971:INFO:rom_table: [2]<e0002000:FPB class=14 designer=43b part=00e> 0006977:INFO:rom_table: [3]<e0000000:ITM class=14 designer=43b part=001> 0006981:INFO:rom_table: [1]<e0041000:ETM-M7 class=9 designer=43b part=975 devtype=13 archid=4a13 devid=0:0:0> 0006981:INFO:rom_table:[1]<e0040000:TPIU-M7 class=9 designer=43b part=9a9 devtype=11 archid=0000 devid=0:0:ca1> 0006986:INFO:cortex_m:CPU core #0 is Cortex-M7 r1p0 0006991:INFO:cortex_m:FPU present: FPv5 0007001:INFO:dwt:4 hardware watchpoints 0007006:INFO:fpb:8 hardware breakpoints, 1 literal comparators 0007028:INFO:server:Semihost server started on port 4444 0007028:INFO:gdbserver:GDB server started on port 3333

Using (\libusb-1.0.21\MS64\dll) 114KB [UNPLUGGED BOARD]
C:\Python27>pyocd gdbserver --pack=C:\python27\Keil.STM32F7xx_DFP.2.12.0.pack Waiting for a debug probe to be connected... [CONNECTED BOARD] 0006200:INFO:board:Target type is stm32f767zi 0006400:INFO:dap:DP IDR = 0x5ba02477 (v2 rev5) 0006505:INFO:ap:AP#0 IDR = 0x74770001 (AHB-AP var0 rev7) 0006510:INFO:rom_table:AP#0 ROM table #0 @ 0xe00fd000 (designer=020 part=451) 0006515:INFO:rom_table:[0]<e00fe000:ROM class=1 designer=43b part=4c8> 0006515:INFO:rom_table: AP#0 ROM table #1 @ 0xe00fe000 (designer=43b part=4c8) 0006520:INFO:rom_table: [0]<e00ff000:ROM class=1 designer=43b part=4c7> 0006520:INFO:rom_table: AP#0 ROM table #2 @ 0xe00ff000 (designer=43b part=4c7) 0006525:INFO:rom_table: [0]<e000e000:SCS-M4 class=14 designer=43b part=00c> 0006530:INFO:rom_table: [1]<e0001000:DWT class=14 designer=43b part=002> 0006530:INFO:rom_table: [2]<e0002000:FPB class=14 designer=43b part=00e> 0006535:INFO:rom_table: [3]<e0000000:ITM class=14 designer=43b part=001> 0006540:INFO:rom_table: [1]<e0041000:ETM-M7 class=9 designer=43b part=975 devtype=13 archid=4a13 devid=0:0:0> 0006540:INFO:rom_table:[1]<e0040000:TPIU-M7 class=9 designer=43b part=9a9 devtype=11 archid=0000 devid=0:0:ca1> 0006545:INFO:cortex_m:CPU core #0 is Cortex-M7 r1p0 0006550:INFO:cortex_m:FPU present: FPv5 0006555:INFO:dwt:4 hardware watchpoints 0006561:INFO:fpb:8 hardware breakpoints, 1 literal comparators 0006580:INFO:server:Semihost server started on port 4444 0006585:INFO:gdbserver:GDB server started on port 3333

Using (\libusb-1.0.22.7\MS64\dll) 119KB [UNPLUGGED BOARD]
C:\Python37>pyocd gdbserver --pack=C:\python37\Keil.STM32F7xx_DFP.2.12.0.pack Waiting for a debug probe to be connected... [CONNECTED BOARD] Exception ignored in: <function _AutoFinalizedObjectBase.__del__ at 0x00000264A8B54550> Traceback (most recent call last): File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 84, in __del__ self.finalize() File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 144, in finalize self._finalizer() File "c:\python37\lib\weakref.py", line 566, in __call__ return info.func(*info.args, **(info.kwargs or {})) File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 104, in _do_finalize_object_ref obj._do_finalize_object() File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 71, in _do_finalize_object self._finalize_object() File "c:\python37\lib\site-packages\usb\backend\libusb1.py", line 604, in _finalize_object _lib.libusb_unref_device(self.devid) OSError: exception: access violation writing 0x0000000000000024 0006425:INFO:board:Target type is stm32f767zi 0006635:INFO:dap:DP IDR = 0x5ba02477 (v2 rev5) 0006715:INFO:ap:AP#0 IDR = 0x74770001 (AHB-AP var0 rev7) 0006730:INFO:rom_table:AP#0 ROM table #0 @ 0xe00fd000 (designer=020 part=451) 0006735:INFO:rom_table:[0]<e00fe000:ROM class=1 designer=43b part=4c8> 0006735:INFO:rom_table: AP#0 ROM table #1 @ 0xe00fe000 (designer=43b part=4c8) 0006745:INFO:rom_table: [0]<e00ff000:ROM class=1 designer=43b part=4c7> 0006745:INFO:rom_table: AP#0 ROM table #2 @ 0xe00ff000 (designer=43b part=4c7) 0006750:INFO:rom_table: [0]<e000e000:SCS-M4 class=14 designer=43b part=00c> 0006750:INFO:rom_table: [1]<e0001000:DWT class=14 designer=43b part=002> 0006755:INFO:rom_table: [2]<e0002000:FPB class=14 designer=43b part=00e> 0006760:INFO:rom_table: [3]<e0000000:ITM class=14 designer=43b part=001> 0006765:INFO:rom_table: [1]<e0041000:ETM-M7 class=9 designer=43b part=975 devtype=13 archid=4a13 devid=0:0:0> 0006765:INFO:rom_table:[1]<e0040000:TPIU-M7 class=9 designer=43b part=9a9 devtype=11 archid=0000 devid=0:0:ca1> 0006770:INFO:cortex_m:CPU core #0 is Cortex-M7 r1p0 0006780:INFO:cortex_m:FPU present: FPv5 0006785:INFO:dwt:4 hardware watchpoints 0006795:INFO:fpb:8 hardware breakpoints, 1 literal comparators 0006825:INFO:server:Semihost server started on port 4444 0006825:INFO:gdbserver:GDB server started on port 3333

Using (\libusb-1.0.22.7\MS64\dll) 119KB [UNPLUGGED BOARD]
C:\Python27>pyocd gdbserver --pack=C:\python27\Keil.STM32F7xx_DFP.2.12.0.pack Waiting for a debug probe to be connected... [CONNECTED BOARD] Exception ignored in: <function _AutoFinalizedObjectBase.__del__ at 0x000001B099C13550> Traceback (most recent call last): File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 84, in __del__ self.finalize() File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 144, in finalize self._finalizer() File "c:\python37\lib\weakref.py", line 566, in __call__ return info.func(*info.args, **(info.kwargs or {})) File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 104, in _do_finalize_object_ref obj._do_finalize_object() File "c:\python37\lib\site-packages\usb\_objfinalizer.py", line 71, in _do_finalize_object self._finalize_object() File "c:\python37\lib\site-packages\usb\backend\libusb1.py", line 604, in _finalize_object _lib.libusb_unref_device(self.devid) OSError: exception: access violation writing 0x0000000000000024 0005904:INFO:board:Target type is stm32f767zi 0006109:INFO:dap:DP IDR = 0x5ba02477 (v2 rev5) 0006194:INFO:ap:AP#0 IDR = 0x74770001 (AHB-AP var0 rev7) 0006204:INFO:rom_table:AP#0 ROM table #0 @ 0xe00fd000 (designer=020 part=451) 0006214:INFO:rom_table:[0]<e00fe000:ROM class=1 designer=43b part=4c8> 0006214:INFO:rom_table: AP#0 ROM table #1 @ 0xe00fe000 (designer=43b part=4c8) 0006224:INFO:rom_table: [0]<e00ff000:ROM class=1 designer=43b part=4c7> 0006224:INFO:rom_table: AP#0 ROM table #2 @ 0xe00ff000 (designer=43b part=4c7) 0006229:INFO:rom_table: [0]<e000e000:SCS-M4 class=14 designer=43b part=00c> 0006234:INFO:rom_table: [1]<e0001000:DWT class=14 designer=43b part=002> 0006239:INFO:rom_table: [2]<e0002000:FPB class=14 designer=43b part=00e> 0006239:INFO:rom_table: [3]<e0000000:ITM class=14 designer=43b part=001> 0006239:INFO:rom_table: [1]<e0041000:ETM-M7 class=9 designer=43b part=975 devtype=13 archid=4a13 devid=0:0:0> 0006244:INFO:rom_table:[1]<e0040000:TPIU-M7 class=9 designer=43b part=9a9 devtype=11 archid=0000 devid=0:0:ca1> 0006244:INFO:cortex_m:CPU core #0 is Cortex-M7 r1p0 0006254:INFO:cortex_m:FPU present: FPv5 0006259:INFO:dwt:4 hardware watchpoints 0006269:INFO:fpb:8 hardware breakpoints, 1 literal comparators 0006294:INFO:server:Semihost server started on port 4444 0006294:INFO:gdbserver:GDB server started on port 3333

ALL four server work with:

Open another Command Prompt Screen:
C:\WINDOWS\system32>cd \Users\kevin\Mbed Programs\mbed-os-example-blinky\BUILD\NUCLEO_F767ZI\ARMC6

C:\Users\kevin\Mbed Programs\mbed-os-example-blinky\BUILD\NUCLEO_F767ZI\ARMC6>arm-none-eabi-gdb

GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417-git Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". (gdb)

(gdb) file mbed-os-example-blinky.elf Reading symbols from mbed-os-example-blinky.elf...warning: Loadable section "RW_IRAM1" outside of ELF segments done. (gdb) target remote localhost: 3333 Remote debugging using localhost: 3333 warning: Loadable section "RW_IRAM1" outside of ELF segments 0x0800be2a in serial_writable () (gdb) load mbed-os-example-blinky.elf Loading section RW_IRAM1, size 0x108 lma 0x200002f8 Loading section ER_IROM1, size 0xed9c lma 0x8000000 Start address 0x80001f8, load size 61092 Transfer rate: 34 KB/sec, 1909 bytes/write. (gdb) [Works ok]

PROBLEM:

C:\WINDOWS\system32>\python37\Scripts\pyocd pack --install stm32f767zi
0000296:ERROR:main:'pack' command is not available because cmsis-pack-manager is not installed

BUT:

C:\Python37>pip install cmsis-pack-manager==0.2.8
Requirement already satisfied: cmsis-pack-manager==0.2.8 in c:\python37\lib\site-packages (0.2.8)
Requirement already satisfied: pyyaml>=3.12 in c:\python37\lib\site-packages (from cmsis-pack-manager==0.2.8) (5.1.2)
Requirement already satisfied: milksnake>=0.1.2 in c:\python37\lib\site-packages (from cmsis-pack-manager==0.2.8) (0.1.5)
Requirement already satisfied: appdirs>=1.4 in c:\python37\lib\site-packages (from cmsis-pack-manager==0.2.8) (1.4.3)
Requirement already satisfied: cffi>=1.6.0 in c:\python37\lib\site-packages (from milksnake>=0.1.2->cmsis-pack-manager==0.2.8) (1.12.3)
Requirement already satisfied: pycparser in c:\python37\lib\site-packages (from cffi>=1.6.0->milksnake>=0.1.2->cmsis-pack-manager==0.2.8) (2.19)``

Please help me with this error:
"'pack' command is not available because cmsis-pack-manager is not installed".
Many thanks, Kevin.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The reported entry point is pyocd pack --install stm32f767zi, which fails while reporting that cmsis-pack-manager is unavailable despite version 0.2.8 being installed. Start by reproducing this Windows command and reviewing the pack command's dependency handling; done means the command works with the installed dependency or the incompatibility is documented with a clear cause.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.