You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I have several target MCUs in different devices I am working on. The pylink library is working great with STM32F401 cores, but I am having problems with an NXP MKL16Z64VFM4 chip.
Using JLink v6.30e, Windows 7, pylink 0.1.0 or 0.0.10
Running Segger J-Link Commander or J-Flash, it is reported that the protection settings in memory 0x400-0x40F indicate readout is disabled. Pressing "OK" triggers a mass erase and subsequent programming through that software succeeds.
However, I cannot do this through the pylink interface. Attempting to connect() to the device, I get one of several issues - not always the same. They include:
PCode returned with error code -1
JLinkException('Unspecified error.',)
Since I cannot connect, I cannot unlock. Related to this, unlocking the Kinetis family appears to be supported in the library, but is it only a subset? I saw mention of K40 and K60 specifically - is the L family not supported?
So, my specific question is - do you have any suggestions for what might be wrong with the connection method? Any debugging tips?
Thanks in advance!
The text was updated successfully, but these errors were encountered:
You can suppress that pop-up (only shows up on Windows actually) by calling disable_dialog_boxes() before calling open(). I believe the DLL has some logic around unlocking as well. I would also look at the unsecure_hook callback that you can pass to the constructor, as you can have that always return to always force unsecuring through the DLL.
Hello,
I have several target MCUs in different devices I am working on. The pylink library is working great with STM32F401 cores, but I am having problems with an NXP MKL16Z64VFM4 chip.
Using JLink v6.30e, Windows 7, pylink 0.1.0 or 0.0.10
Running Segger J-Link Commander or J-Flash, it is reported that the protection settings in memory 0x400-0x40F indicate readout is disabled. Pressing "OK" triggers a mass erase and subsequent programming through that software succeeds.
However, I cannot do this through the pylink interface. Attempting to connect() to the device, I get one of several issues - not always the same. They include:
JLinkException('Unspecified error.',)
Since I cannot connect, I cannot unlock. Related to this, unlocking the Kinetis family appears to be supported in the library, but is it only a subset? I saw mention of K40 and K60 specifically - is the L family not supported?
So, my specific question is - do you have any suggestions for what might be wrong with the connection method? Any debugging tips?
Thanks in advance!
The text was updated successfully, but these errors were encountered: