Hi everyone,

2 years ago, we used a Segger Flasher Arm as a production tool for programming CYBLE-022001-00, and it worked really well. Then, the programmer stayed on the shelf for ~1.5 years and now it does not work.

We reprogrammed it with the same config, but the Flasher says it can't connect to the microcontroller. However, if I program the MCU first with a PSoC Programmer, I can then connect to it with the Segger Flasher ARM without any problems.

It seems like we have the same problem as this thread: forum.segger.com/index.php?page=Thread&threadID=2945

Since it worked two years ago but not right now, is it possible that the Flasher is damaged? If not, can you tell me some debugging steps I can do to fix this problem?

Thank you,

Fred

Hi Nino,

• Are you trying to program custom hardware or an eval board?
  

It is custom hardware.

• What target device are you selecting for connection?
  

We select the CYBL10xxx device, as our own is not listed (CYBLE-022001-00), but the CYBL10xxx has the same amount of Flash (128k) and RAM (16k) as our device. I also tried the CY8C4127xxx.

• Could you try to connect to the target device using the J-Link commander and post a screenshot of the connection?
  

I attached a screenshot of the J-Link Commander window that can't connect ("J-Link Commander can't connect.PNG").

• Does that generally work?
  

J-Link can't connect. However, it did two years ago.

• Could you attach the config file you are using for programming?
  

I can't attach the config file, as it contains our .hex. However, as said in the forum I posted, it's probably because the SWD pins of the Cypress' chip are configured initially in GPIO mode, instead of in SWD. Thus, my problem could be replicated with any other valid .hex.

• Could you also attach a J-Link log file of the failing connection?
  

I have attached a LOG file ("JLinkARM didn't work.log.txt") of what happens when I try to program the PRoC using the Flasher. I didn't attach the log file of when it works after I've programmed it with the PSoC Programmer, as the LOG file looks like it prints the .hex data. However, I attached a screenshot of the JFlash window after it successfully programmed the PRoC ("JFlash worked - redacted.png").

I hope that helps troubleshooting the problem.

Thanks,

Fred

Hi Nino, thank you for the answer.

Unfortunately, selecting a generic M0 does not work for me, even after I have programmed it with the PSoC Programmer. I get a "Selected data does not fit into selected flash sectors" error, and I can't connect to the MCU either.

The same setup that we used 1.5 years ago does not work now, with the difference being that the Segger Flasher ARM stayed on the shelf for 1.5 years.

Have you looked at the forum post that I included in my first comment? This problem looks a lot like ours. It seemed that the problem was fixed at that time in version 5.10p of JFlash, but I tried this version and the newest and I still have the problem.


Thanks,


Fred

Hi Nino,

Thank you for the time you're taking to help me.

It was the same setup. The Flasher ARM was on the shelf for 1.5 years, and when we plugged it back (no computer, only using the config file that was in it), it did not work anymore.

Now, of course, I'm debugging at my station, so the firmware in the Flasher has been updated, and the version of JFlash is not the same (although I did try the same as before).

I disagree when you say that the forum I attached is completely unrelated.

The MCU they used is CYBL10461-56LQXI (PRoC with BLE)
The MCU we use is CYBLE-022001-00 (PRoC with BLE)


So while their MCU is more powerful, they're still both PRoC for BLE, and both use SWDIO for programming, with an XRES pin.




I understand that this is not a supported device. I'm however stumped that something that worked 1.5 years ago just stopped working, without the Flasher being updated.


Thank you,


Fred