ATmega328P Xplained Mini - mEDBG - TCF Error code: 131118

Go To Last Post
2 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

Following the instructions in the Power Debugger User Guide for turning the Target power on & off on an ATmega328P Xplained Mini board:

 

 

 https://www.microchip.com/en-us/development-tool/atpowerdebugger

https://ww1.microchip.com/downloads/en/DeviceDoc/40002201A.pdf

 

The commands do seem to work - the Target power goes off & on - but the -pson command (to turn the power back on) always gives an error:

C:\>atprogram.exe -t medbg parameters -psoff
Firmware check OK
OK

 

C:\>atprogram.exe -t medbg parameters -pson
Firmware check OK
[ERROR] Failed sending command/receiving response. Command ID 0x2b. Failed sending CMSIS command from AtmelDapTransport. (TCF Error code: 131118)

 

C:\>

 

What does it mean?

 

Is it safe to ignore it?

 

 

ADDENDUM

 

With 'verbose' output:

C:\>atprogram.exe -v  -t medbg parameters -psoff
[DEBUG] Starting execution of "parameters"
[DEBUG] Starting process 'C:\Program Files (x86)\Atmel\Studio\7.0\7.0\atbackend\atbackend.exe'
[DEBUG] Connecting to TCP:127.0.0.1:62648
[INFO] Connected to medbg, fw version: 1.16
Firmware check OK
[INFO] Firmware check OK
OK
[DEBUG] Command "parameters" finished with return code 0
[DEBUG] Exit successfully.

 

C:\>atprogram.exe -v  -t medbg parameters -pson
[DEBUG] Starting execution of "parameters"
[DEBUG] Starting process 'C:\Program Files (x86)\Atmel\Studio\7.0\7.0\atbackend\atbackend.exe'
[DEBUG] Connecting to TCP:127.0.0.1:62652
[INFO] Connected to medbg, fw version: 1.16
Firmware check OK
[INFO] Firmware check OK
[ERROR] Failed sending command/receiving response. Command ID 0x2b. Failed sending CMSIS command from AtmelDapTransport. (TCF Error code: 131118)

 

C:\>

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
Last Edited: Tue. Oct 19, 2021 - 04:45 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, it depends how you pronounce that famously awesome switch: " -psoff " :)

(That's no way to talk to a medbg!)

 

Seriously: I guess it could be timing-related in getting across an impatient cmsis-dap layer.  There is no real way this command can fail.

Safe to ignore, I think.