Open Hoohaha opened 4 years ago
Looks like a strange combination of issues. The logic is supposed to terminate scanning APs after it gets 2 invalid AP ID register reads in a row (ID == 0). So reading the AP's ID must have returned a non-zero value? That's very odd. In fact, the ID seems to have indicated the APs are all MEM-APs, otherwise you wouldn't see the _init_hprot()
call in the backtraces.
I'm not sure what the right thing to do here is. If pyocd sees a non-zero AP ID, it should examine the AP.
Can you tell me more about the system? We can talk via email.
@flit os: windows 7 + kinetis frdmk66f. This is low priority. I will continue to monitor this issue on new version of pyocd.
I did not expect K66F! That's surprising. Are there any special conditions that might have triggered this, such as low power states?
version: 0.27
There are many exceptions(255) displayed in terminal when pyocd cannot read aps. It's very unfirendly. Can we change the level to debug or disable the traceback or another way to fix that?