AnsweredAssumed Answered

PE multilink JTAG/BDM Kinetis programming issue

Question asked by Amit Kumar on Jan 24, 2014
Latest reply on Mar 10, 2016 by anju m

Like • Show 2 Likes2
Comment • 27

I am trying to program K20 custom board but it is showing an error.

after clicking yes, the same msg appear and again I click yes then following error comes

these two error msg comes after one another and it doesn't program. Kindly look into the matter initially I had the same issue for K10 board. I tried everything but It didn't worked. PE multilink universal not detecting K10 uc I thought that there might be some soldering issue as it was a QFN package. so I changed my design and added MK20DX128VLF5(LQFP) we bought 100 pcs of this uc and 100 pc of KL05 , 30 pc of K10. we checked for K10 and K20 uc it doesn't work. I checked PE multilink by programming FRDM-KL46Z board through SWD connecter J6, it is programming the board without any issue. I went through the KQRUG user guide which I found out from my previous query regarding K10 board through the community. and I also went through the PE4576-Technical summary. and tried resolving the issue but didn't resolve then after bashing my head I somehow managed to find an app note on programming kinetis uc i.e AN4835 which I think is supposed to be mention in the datasheet as no user will get to know that there exist an app note for how to program the Kinetis uc. There are many engineers who will be working on ARM cortex uc but if there is not much resources then why will they choose freescale. Kindly look into the matter and make the programmer work as I fear all the above controller i.e (100 K20, 100 Kl05, 30 K10) uc will be collecting dust. Already we have 100 k20 boards ready. The following diagram shows the connections I have tried for different modes(JTAG/SWD) for programming K20 board.

it didn't worked then i tried SWD config

In both the cases I connected VCC(3.3V) ----->TVCC(PIN 1)

and GND----> GND(PIN 4) of PE multilink universal. I am using the following port from PE multilink universal.

I probed RESET_b pin in normal condition it is logic high(3.3V) and while programming it becomes logic low(0V).

The above is the testing breakout board(dual side).

I hope The community will help me to resolve this issue ASAP. Our expected target is 100,000 kinetis units this year In our line of products.

Thanks and Regards

Amit Kumar

Jorge_Gonzalez

Jan 27, 2014 12:49 AM

Correct Answer

Hello Amit:

Thanks for considering my suggestions. About your comments and some more inputs:

5) This should not be critical, but try replacing that 1K resistor with one of 4.7K - 10K. Also confirm that you have the R2 10K pull - up resistor connected to pin 21, and measure voltage in that pin to verify that it is always in high level.

Now, the 1.64 V is definitely not correct, the value should be near the 3.3 V when not asserted. This seems to indicate that the MCU is constantly resetting. You need to watch that pin with an oscilloscope.

If the device is resetting, this may solve the issue:

- Make sure to select "Always mass erase on connect", and select a not so high debug frequency (e.g. 0.10 MHz).

Then follow the next steps:

1) Disconnect the board from your 3.3 V source.

2) With a jumper force the reset pin to a low level (GND) and hold it.

3) Power on the board (connect the 3.3 V source). Do not release reset yet.

4) Start a debug session and as soon as it is starting release the reset button.

Try this more than once.

Additionally, you could also try mass erasing the K20 device from the Flash programmer. Just open the programmer, select proper connection and specific flash configuration file and then click on "Erase Whole Device".

If the Erase is successful, then you should be able to debug.

Let me know what you find.

Regards!

Jorge Gonzalez

See the reply in context

No one else had this question

Outcomes

27 Replies

Jorge_Gonzalez Jan 26, 2014 4:58 PM
Mark Correct
Correct Answer
Hello Amit:

Let me throw some suggestions and questions trying to help:

1) Are you connecting VSS to GND (MCU pin 23)?. Sorry if this is a silly question, but from your board picture I cannot see the other side and I just see a capacitor in there.

2) Again, most probably you have checked it, but just to make sure, do you see both LEDs ON when connecting your Multilink?

3) You connected GND to PIN 4 of Multilink. The ARM JTAG interface specs recommend to connect all the GND pins, not only pin 4 (pins 4/6/8/10/12/14/16/18/20). This is to reduce noise.\

4) You are not using a standard 20 pin header in your custom board, so I assume you are connecting your Multilink with jumper wires. In this case you have to make sure that these wires are as short as possible. In several cases large cables have caused connection problems.

5) Try reducing the PE Universal Multilink debug speed. This can be done from the tab Run -> Debug Configurations -> Edit. As your MCUs are brand new, I also recommend to check the "Always mass erase on connect" option. And last, for your second schematic (using SWD instead of JTAG), you have to make sure to select the "Use SWD ..." option. See the next images for these comments:

6) And finally, I have known of cases in which the debug configurations get corrupted. Easiest way to discard this is to create a new empty bareboard project and trying to program this in your MCU, but considering my points above as well.

I hope some of this guides you to the solution. Let us know about further findings.

Regards!
Jorge Gonzalez
Like • Show 2 Likes2
Actions
- Amit Kumar @ Jorge_Gonzalez on Jan 26, 2014 9:55 PM
  Mark Correct
  Correct Answer
  Hi Jorge
  Thanks for the quick reply. I have followed your suggestions. what I did was :
  1. I removed all the external connections and checked the continuity of the board. vdd(+3.3V) is connected to pin nos 1, 9, 10, 16, 22 and the VSS(GND) is connected to pin nos. 2, 11, 12, 23.(Its a dual sided board)
  2. As per the multilink universal guideline i.e its given below, I followed and ensured both the LEDs are glowing.
  
  3. I have connected all the ground pins (2,4,6,8,10,12,14,16,18,20) of multilink externally. (although multimeter shows that all the gnd pins are shorted internally when not connected)
  4. I have checked that there is no loose contact with the jumpers, and the length of the jumper is around 15 cm.
  5. According to the 1st schematic, value for R1(resistor to reset pin) is 1K. when I probe this pin, In normal condition I get 1.64V and when the programming starts it becomes (0V). Is that expected?? I mean the voltage 1.64v? or should it be higher?
  6. I tried your 5th point i.e 1st checked for SWD, and then for JTAG.
  7. I tried making empty bareboard project and programming it.
  
  In this case It didn't asked for secure, it directly stated that multilink is not communicating i.e 2nd image which I shared in my 1st post.
  
  The above configuration is for SWD now Trying for JTAG. It still didn't worked. what should I do next?
  
  Thanks and Regards
  Amit Kumar
  Like • Show 0 Likes0
  Actions
  - Jorge_Gonzalez @ Amit Kumar on Jan 27, 2014 12:49 AM
    Unmark Correct
    Correct Answer
    Hello Amit:
    
    Thanks for considering my suggestions. About your comments and some more inputs:
    
    5) This should not be critical, but try replacing that 1K resistor with one of 4.7K - 10K. Also confirm that you have the R2 10K pull - up resistor connected to pin 21, and measure voltage in that pin to verify that it is always in high level.
    
    Now, the 1.64 V is definitely not correct, the value should be near the 3.3 V when not asserted. This seems to indicate that the MCU is constantly resetting. You need to watch that pin with an oscilloscope.
    
    If the device is resetting, this may solve the issue:
    
    - Make sure to select "Always mass erase on connect", and select a not so high debug frequency (e.g. 0.10 MHz).
    
    Then follow the next steps:
    
    1) Disconnect the board from your 3.3 V source.
    2) With a jumper force the reset pin to a low level (GND) and hold it.
    3) Power on the board (connect the 3.3 V source). Do not release reset yet.
    4) Start a debug session and as soon as it is starting release the reset button.
    
    Try this more than once.
    
    Additionally, you could also try mass erasing the K20 device from the Flash programmer. Just open the programmer, select proper connection and specific flash configuration file and then click on "Erase Whole Device".
    
    If the Erase is successful, then you should be able to debug.
    
    Let me know what you find.
    
    Regards!
    Jorge Gonzalez
    Like • Show 1 Like1
    Actions
    - Amit Kumar @ Jorge_Gonzalez on Jan 27, 2014 5:05 AM
      Mark Correct
      Correct Answer
      Hi Jorge
      I Tried the steps you mentioned but it didn't worked. I then removed all external connections and probed to each pins of the uc(all the connections present in the schematic is still connected) to the oscilloscope and found that pin nos.
      1----> 3.30V
      9,10-----> 3.30V
      16--->3.30V
      18--->3.29v
      20---->3.30v
      21---->3.29v
      22---->3.30v
      26---->1.64v
      For the reset pin I was also doubtful so I soldered the pinout board for KL05 and checked for the reset pin there. On kl05 reset pin I got 1.64v. for the reset pin if I am not connecting any capacitor then getting the following pulse
      
      after connecting the 1uf capacitor I am getting the following waveform
      
      Now what you suggest me to do ? These voltages are when multilink is not connected to the uc. even after connecting the same results exist. These waveforms are common for both k20 and kl05 uc.
      
      Regards
      Amit Kumar
      Like • Show 0 Likes0
      Actions
      - Jorge_Gonzalez @ Amit Kumar on Jan 27, 2014 4:07 PM
        Mark Correct
        Correct Answer
        Hello Amit:
        
        Your MCUs are constantly resetting. This is because they are virgin and the watchdog is enabled. First thing you should do with a new MCU before trying to debug is a mass erase. So we need to forget about the debugger right now and try to erase the whole device using the Flash Programmer (thunderbolt icon).
        
        Your second picture also shows that the capacitor is holding the voltage. So please follow the next steps:
        
        1 - Remove the capacitor.
        2 - Connect your multilink and open the flash programmer (the one that says Flash File to target as in my previous respose).
        3 - Select the FLASH PnE U-Multilink connection, and select also the correct Flash configuration file. You may try with JTAG or SWD, just make sure to click on "Edit" and that the SWD option is checked/unchecked accordingly.
        4 - Click on Erase Whole Device
        
        You should read a message in the console indicating "Erase Command Succeeded".
        
        If this does not work, repeat the procedure but this time with the steps suggested in my previous post, which are:
        
        - Connect Multilink and open flash programmer.
        - Disconnect board power.
        - Hold reset low.
        - Power on the board.
        - Click on "Erase Whole Device" and then release the reset line.
        
        Also, I received feedback from a colleague that 15 cm jumpers are still long in some cases. Could you try with even shorter cables?
        
        It would be great if you can post here a picture showing your connections all the way from the header in your multilink to the pins in your custom board.
        
        Regards!
        Jorge Gonzalez
        1 person found this helpful
        Like • Show 1 Like1
        Actions
        Amit Kumar @ Jorge_Gonzalez on Jan 27, 2014 11:33 PM
        Mark Correct
        Correct Answer
        HI Jorge
        I Tried the steps you mentioned (including removing the capacitor) even holding the reset pin to gnd and after clicking mass erase releasing it. but still the error persists....below is the screenshot if you can see the console window in it.
        
        for the jumper length of jumper
        
        I tried for kl05 it worked i.e it got mass erased and now programs are being dumped in it without any error. But for k20 it is still showing the same error... in KL05 there is only SWD but in k20 there is JTAG, EZPort, SWD. Is there anything else I need to do if I am focusing for SWD in k20 apart from the above schematic? as SWD worked for KL05 using the PE multilink universal(PORT B).
        
        Regards
        Amit Kumar
        Like • Show 0 Likes0
        Actions
        Jorge_Gonzalez @ Amit Kumar on Jan 28, 2014 10:40 AM
        Mark Correct
        Correct Answer
        Hi Amit:
        
        Good to know about the KL05 working.
        
        The procedure is the same for the K20 (just make sure to check the "SWD.." option in the connection).
        
        The only difference I see in your SWD schematic is the pin 21 without pull up, besides of removing capacitor and changing R1 from 1K to 10K.
        
        Have you assembled more than one K20 board? or just that one in your picture?
        
        I would try with another board with the K20 to discard that the MCU is somehow secured or bricked.
        
        Regards!
        
        Jorge Gonzalez
        Like • Show 0 Likes0
        Actions
        Amit Kumar @ Jorge_Gonzalez on Jan 28, 2014 8:36 PM
        Mark Correct
        Correct Answer
        Hi Jorge
        I Have replaced the 1k with 4.7K at reset circuit and have also connected the 10k pullup at pin no 21. before trying with the new uc I wanted to ask you one thing ,in the following image there is an option for JTAG and cJTAG /SWD I tried both but it didnt worked.. which one is recommended?
        
        and also while flash programming there is an option to choose the configuration file, which one is recommended ? I tried with the default configuration file then later I tried with all available configuration file for K20DX128.
        
        Regards
        Amit Kumar
        Like • Show 0 Likes0
        Actions
        Jorge_Gonzalez @ Amit Kumar on Jan 28, 2014 8:58 PM
        Mark Correct
        Correct Answer
        Hello Amit, about your questions:
        
        - The default mode in Kinetis K is JTAG, so I'd go for that. This setting is not relevant right now, as you need to be able to mass erase your K20 first from the flash programmer.
        
        - If your MCUs have a 'Z' in the name (on the top of the chip), then select K20DX128Z.xml, otherwise select the K20DX128.
        
        If you could share with me a picture of your connections from the Multilink to the board that would be helpful.
        
        Regards!
        Jorge Gonzalez
        Like • Show 0 Likes0
        Actions
        Amit Kumar @ Jorge_Gonzalez on Jan 29, 2014 1:40 AM
        Mark Correct
        Correct Answer
        HI Jorge
        Below is the picture of my connections of PE multilink universal with my test board.
        
        I think it will be tuff for you to see the connections so I have made the connection diagram below
        
        Hope the image is clear .
        
        Regards
        Amit Kumar
        1 person found this helpful
        Like • Show 0 Likes0
        Actions
        Jon Gronholz @ Jorge_Gonzalez on Jan 29, 2014 3:45 AM
        Mark Correct
        Correct Answer
        HOORAYY!!! I just got my custom K10 board working after reading the above!
        
        The board I got working is shown on the right. I mounted only the K10, a 3.3V regulator, one bulk 10uF on the regulator output, and one SMD 10k pull-up on reset.
        There is a debug adapter board covering the top half of my mainboard; it has only the Cortex Mini-10 pin header and one 1uF capacitor on reset mounted.
        There is another board covering the bottom half of my mainboard; it has only a DC barrel jack on it, connected to the regulator input.
        I removed the 1uF from reset while following along through the steps above, but I'm not 100% sure that was necessary.
        A 10k PTH resistor is attached to the debug adapter between 3.3V and EZP_CS. I'll put this on the mainboard's next revision.
        The 10k resistor on the breadboard (upper) is connected to 3.3V and SWDIO.
        The <100ohm resistor on the left is connected to VTREF and 3.3V. It was recommended in something I read trying to fix my problem, but is unnecessary; jumper wire is fine.
        The connector on the far left is for the Mini-10 cable that came with the Multilink which is about a mile long (~12" actually).
        The left-most Mini10 adapter is the only one with pin numbers matching the Cortex spec/cable; the two identical adapters I used reversed the pin order, while a mistake on the debug adapter swapped every two pins. With the corrections I'm making, the standard cable should hook directly up and work.
        My chip was rebooting like yours, but by the time I had fixed my mistakes, I no longer needed to do the reset trick described; it mass erased on the first try and then programmed on the first try. I suspect I could have skipped the mass erase. So, I put a PWM LDD in my project, deployed, and stuck a UV LED into the socket and HELLOOOOOO BLINKY!!!! (Thanks Jorge! and good luck Amit!)
        Like • Show 2 Likes2
        Actions
        Amit Kumar @ Jon Gronholz on Jan 31, 2014 10:22 PM
        Mark Correct
        Correct Answer
        Congratulation Jon !!!
        Good to hear that you got benefited from this post.
        Like • Show 0 Likes0
        Actions
    - Amit Kumar @ Jorge_Gonzalez on Jan 31, 2014 9:42 PM
      Mark Correct
      Correct Answer
      Thanks Jorge!!
      
      I made a new board with a different K20 uc and there I added 20 pin header and that got mass erased and is working fine. I was able to program custom made K-60 board also !!!. I think with the controller in which only SWD pins are there for programing, needs to be programmed using SWD mode only and for the controller in which SWD/JTAG and EZport is present needs to be programmed with JTAG mode. I Tried with SWD but that didn't worked JTAG worked successfully there, for KL05 swd worked.
      I have also made a post in which I have described the shortcut process.How To Sucessfully Program a Custom made Kinetis Microcontroller Board.
      but I feel in datasheet it should be mentioned that all new controller should be programmed in a different way for the1st time programming.
      Regards
      Amit Kumar
      Like • Show 3 Likes3
      Actions
      - Jorge_Gonzalez @ Amit Kumar on Feb 3, 2014 8:37 AM
        Mark Correct
        Correct Answer
        Hello Amit:
        
        Sorry I've been a little busy. It is great you finally got positive results!!. I agree about the JTAG/SWD modes (although I am not sure why it did not work in SWD, I will try to investigate this), and also with the mass erase info.
        
        I need to thank you a lot because this thread and the document you just created are going to help many people, as Jon above for example.
        
        Kind Regards!
        Jorge Gonzalez
        Like • Show 0 Likes0
        Actions
        Jose Ribeiro @ Jorge_Gonzalez on Aug 21, 2014 4:41 AM
        Mark Correct
        Correct Answer
        Hello,
        
        I'm now testing our first Kinetis MK22FX512VLK12 custom controller board.
        In our design we included a SWD programming connector (VCC, GND, SWD_DIO, SWD_CLK, RESET). These pins are connected to the PEMicro Multilink Universal (firmware v6.10) Port B (TVCC, GND, TMS/SWD_DIO, TCK/SWD_CLK).
        
        After several attempts using the SWD interface I always get a "Device is secure" message on CW 10.6 and KDS 1.1.0. This is the same behavior as described by Amit.
        
        I also managed to tweak the board and I added TDI and TDO. It works, but I'm looking for a way to use SWD interface.
        
        The Kinetis MCUs use JTAG at reset state, but they can switch from JTAG to SWD mode using a sequence on TMS and TCK, so the Multilink should be able to send this command. (reference manual page 210 - 9.2.1 JTAG-to-SWD change sequence)
        
        It seams that only Eric Styger was successfully using SWD on K20 using the Multilink programmer.
        You can check it here http://mcuoneclipse.com/2014/08/09/hacking-the-teensy-v3-1-for-swd-debugging/
        
        This is his board schematic:
        
        Comparing his solution to mine:
        1 - I'm using Multilink Port B instead of Port G. Pins are short circuit, so...
        2 - My board has a 10k pullup on Reset (it is recommended by Freescale, should I remove it?)
        3 - Kinetis K22 vs K20...
        
        Best regards,
        
        Jose
        Like • Show 0 Likes0
        Actions
        Amit Kumar @ Jose Ribeiro on Aug 21, 2014 4:59 AM
        Mark Correct
        Correct Answer
        Hi Jose
        Please follow these steps How To Sucessfully Program a Custom made Kinetis Microcontroller Board. Altough this document is a summary of the above thread but I think it might help you.
        
        Kind Regards
        Amit Kumar
        Like • Show 0 Likes0
        Actions
        Jose Ribeiro @ Amit Kumar on Aug 21, 2014 10:40 AM
        Mark Correct
        Correct Answer
        Hi Amit,
        
        I have already done those steps yesterday and thanks to you I was able to debug it but only if I use JTAG (btw, I can debug it without the EZP_CS pullup...)
        The problem is that SWD never works. Can't even mass erase the device using SWD. I think you couldn't use SWD also, am I right?
        We need to ask Erich Styger how he managed to debug using SWD...
        
        Best regards,
        
        José Ribeiro
        Like • Show 0 Likes0
        Actions
        ramesh darla @ Jose Ribeiro on Aug 21, 2014 8:33 PM
        Mark Correct
        Correct Answer
        Hi Jose
        
        Few Suggestions for SWD program in K series
        
        1. For mass erase of device No need to be pull-up of EZP_CS_b pin. It will erase the device if you connect GND to all GND of PE Microlink SWD_CLK, SWD_DIO and RESET.
        
        these four pins are must
        
        2. Where as if you want debug/program in SWD mode EZP_CS_b should be pulled up with 10k resistor.(EZP_CS_b pulling up is must for SWD/JTAG)
        
        Please check the connections at Connector wether it is touching properly or not. Try with direct soldering on the brd.
        
        3. And you need select use SWD pin reduce option in Codewarrier
        
        Hope it will help you. I am able to program my device in SWD as well JTAG mode
        
        rgds
        darla
        Like • Show 0 Likes0
        Actions
        Amit Kumar @ Jose Ribeiro on Aug 21, 2014 11:12 PM
        Mark Correct
        Correct Answer
        Hi Jose
        
        I just checked if the K20 is being programmed or not using SWD and it did. attached is the test code which I compiled in CW10.5 Kindly check the settings done in the run configuration. One Suggestion I would like to give you is in your custom board place 20 pin header and connect the appropriate pins to it as in case of wired connections, the wires can induce noise which can cause this issue. I was not able to program the board shown in the above thread instead I had to design a new board containing 20 pin header along with 10 gnd pins connected to the board's ground. I know all the ground is shorted in PE multilink but these ground accompanying with the swd/jtag pins are there to provide isolation from noise. after doing these changes my board worked. I just realized that you are using PORT G so in that connect all the gnds to the board gnd. Rest I hope you have already connected as required.
        
        Kind Regards
        Amit Kumar
        Attachments
        K20_SWD_Test.zip743.7 KB
        Like • Show 1 Like1
        Actions
        Jose Ribeiro @ Amit Kumar on Aug 22, 2014 4:32 AM
        Mark Correct
        Correct Answer
        DONE!
        
        I added a SWD_DIO 10k pullup and a SWD_CLK 4k7 pulldown + 66pF.
        The problem was solved. I can now debug even using a 1 meter jump cable with only 5 wires!
        BTW, I think you can use only 4 pins as long as you inject 3.3V on the TVCC Multilink connector. This can be interesting for small controller boards.
        
        For the capacitor value use a 66pF - 1nF.
        
        This explains why you recommend to connect all GNDs... I think that PEMicro should increase immunity. Maybe it will be as easy as increasing a delay...
        
        Thank you all for your support!
        
        Best regards,
        
        Jose
        Like • Show 0 Likes0
        Actions
kayathri M Aug 24, 2014 11:13 PM
Mark Correct
Correct Answer
Hi,

We are using our customized K70 board. We use JTAG for debugging. Previously it was not debugging at all. After we pulled up the reset pin using 10k, we are able to debug ,but the device gets disconnected after around 2 minutes. Reset pin is also pulsing continuously. Kindly suggest us the steps to be followed further.

Regards,
Kayathri M
Like • Show 0 Likes0
Actions
- ramesh darla @ kayathri M on Aug 24, 2014 11:26 PM
  Mark Correct
  Correct Answer
  Hi kayathi
  
  This is most probably connections issue make sure your connector properly connected and check by direct soldering for verification.
  
  Make sure that EZP_CS_b pin pulled high for JTAG/SWD program.
  
  thanks
  darla
  Like • Show 0 Likes0
  Actions
- Amit Kumar @ kayathri M on Aug 25, 2014 12:04 AM
  Mark Correct
  Correct Answer
  Hi Kayathi
  
  Please follow these steps
  1. Probe the reset pin and check if the waveform matches with the waveform on this thread. It might be that your uc is still not flashed. In that case follow the instruction How To Sucessfully Program a Custom made Kinetis Microcontroller Board.
  2. In case the reset pulsing is random, There might be some soldering issue. or some pins might have been shorted. What is the voltage on reset pin?
  
  Regards
  Amit Kumar
  Like • Show 1 Like1
  Actions
kayathri M Aug 25, 2014 4:03 AM
Mark Correct
Correct Answer
Hi darla & Amit Kumar

Thank you for your instant replies. EZP_CS_b pin has been pulled high. I have attached reset waveform captured before and after disconnection. What do they imply?

Regards
Kayathri
Like • Show 0 Likes0
Actions
- Amit Kumar @ kayathri M on Aug 25, 2014 4:21 AM
  Mark Correct
  Correct Answer
  Hi Kayathri
  Can you share the schematic of the reset circuitry? If you are using a cap connected to reset pin please remove it. For flashing the uc u need to remove the cap. but let the 10K pullup be connected to the reset pin. after doing that repeat the steps.
  Generally reset pin should show 3.20 V but in your 1st waveform the voltage shown is 2.0 V. Attached is the waveform of reset pin which I have recorded from my K60 board.
  
  Kind Regards
  Amit Kumar
  Like • Show 0 Likes0
  Actions
Mario Gongora Nov 6, 2015 3:06 PM
Mark Correct
Correct Answer
Hello Amit, Jorge!!

I want to say thank you about this post, very helpul and give me a lot of advices on how to implement correctly my own k20 custom board. I'am using mk20dx256vlh7, same as Teensy 3.1 onboard.

I have to recognize that it doesn't work at first attempt, but finally done!!

About the problem with SWD debugging, I'm able to use JTAG/SWD, this is thanks to Jose Ribeiro contribution:

"I added a SWD_DIO 10k pullup and a SWD_CLK 4k7 pulldown + 66pF"

Excellent work to all!!

BR

Mario
Like • Show 0 Likes0
Actions
anju m Mar 10, 2016 2:08 AM
Mark Correct
Correct Answer
hello all,
iam trying to program mk60fx512 using multilink fx jtag. Iam getting the following error ...

Device selected is k60fx512
User Specified Hardware Selection : Interface=USBMULTILINK and Port=USB1
Connecting to target.
P&E Interface detected - Flash Version 9.33
Forcing mass erase...
Can not enter background mode .
Unable to initialize PEDebug.
PE-ERROR: Failed to Initialize Target

How to solve this.Please help
Like • Show 0 Likes0
Actions

PE multilink JTAG/BDM Kinetis programming issue

Outcomes

Attachments

Related Content

Recommended Content

Incoming Links

NEWS