Wednesday, January 24th 2018, 10:31am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Giteh

Beginner

Date of registration: Jan 8th 2018

Posts: 4

1

Monday, January 8th 2018, 11:59am

Cannot connect to PIC32MZ2048EFM100 via ICSP

Hello,

I' ve got problem with programming PIC32MZ2048EFM100 by J-Link Commander via ICSP.
I also tried to program via J-Flash Light. What is strange I tried to erase PIC many times and only one time it has ended with success and about 20 times with an error.
I attach the screenshot from J-Link Commander.

Best regards.
Giteh has attached the following image:
  • Przechwytywanie.PNG

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 574

2

Tuesday, January 9th 2018, 9:46am

Hello,

Thank you for your inquiry.
Such an issue is not known to us.
Are you using an eval board or custom hardware?
Did you have a working setup before?
What J-Link software version were you using then?
Are you using an external J-Link or an OB?
Could you attach schematics that show the debug connection between J-Link and target device?

Best regards,
Nino

Giteh

Beginner

Date of registration: Jan 8th 2018

Posts: 4

3

Tuesday, January 9th 2018, 11:27am

Hi,

I'm using custom hardware.
J-Link works fine with MK24 Kinetis MCU on the same board.
I'm using external J-Link (version 10.1) with newest firmware: 6.22d.
I've connected J-Link to the device as it is shown on scheme of the Microchip Adapter -
TMS -> ICSPData
TCK -> ICSPClk
GND -> GND
VTREF -> VDD
#RESET -> #MCLR

I attached schema of the Microchip Adapter.

After connecting via MPLAB IDE (3.65) it returns:

Quoted

Connecting to JLink Probe...
Connection Failed
MPLABComm returned an error code of -406, System (Linux/OSX errno.h) error value 106.


Best regards,
Patryk
Giteh has attached the following image:
  • microchip_adapter.PNG

Giteh

Beginner

Date of registration: Jan 8th 2018

Posts: 4

4

Tuesday, January 9th 2018, 2:42pm

Hi,

I didn't add pull-up resistors to TMS and TCK signals at firsts.
Now I added 10kΩ pull-up resistorto TMS and TCK.

At the beginning it worked. I was able to erase PIC, but when I'm trying to do this again attached statement shows.

Best regards,
Patryk
Giteh has attached the following image:
  • screen.PNG

This post has been edited 1 times, last edit by "Giteh" (Jan 9th 2018, 2:49pm)


SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 574

5

Wednesday, January 10th 2018, 4:05pm

Hello Patryk,

We just tried to reproduce the issue but could connect to a PIC32MZ2048EFM100 via ICSP just fine.
So the issue is most likely related to a setup problem on your hardware.
The schematics you provided are simply taken from the Microchip Adapter Schematic: https://www.segger.com/products/debug-pr…rochip-adapter/
That is not what I asked for. Could you post the schematics of the debug interface on *your* custom hardware that shows how the ICSP debug connector is connected to the target device (PIC32)?

Are you using the Microchip Adapter sold by SEGGER to connect to J-Link?
Which of the connectors are you using? The 14-Pin MIPS or RJ12?
The error message claims that TDO is pulled high. Is this the case on your setup?

Best regards,
Nino

Giteh

Beginner

Date of registration: Jan 8th 2018

Posts: 4

6

Friday, January 12th 2018, 12:14pm

Hello Nino,

I attache schematic which shows how the ICSP debug connector is connected to the target device, but please notice that as I told in post number 4 I added pull-up resistors (10kΩ) to the lines TMS and TCK.
I added pull-ups due to interface description which I also attache.
After that statement of the J-Link Commander have changed.

What is strange J-Link Commander said that TDO pin is constant high, but I didn't connect this pin at all.

Could You tell mi something more about those pull-ups?
Is that connection correct?

Best regards,
Patryk
Giteh has attached the following images:
  • pic32mz_cut.PNG
  • pull_ups.PNG

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 574

7

Wednesday, January 17th 2018, 4:38pm

Hello Patryk,

Do you have an Microchip eval board to test your setup against?
Generally we suggest first getting a running eval board setup and then design custom hardware based on that.

For reference for our testing we used an Explorer 16 Development Board.
First verify functionality with an eval board.
Then see how the eval board has wired the ICSP connector and copy that design.
That should do the trick.

Please understand that we can't put more time in this case as there is no issue with J-Link or the ICSP interface but exclusively a custom hardware issue.

Best regards,
Nino