Search Results
Search results 1-11 of 11.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Hi Michael, It is indeed custom hardware, but I will try to reproduce the issue with a CYBLE-022001-EVAL. As the problem only happens in standalone mode and not with JFlash, I believe it will be reproducible. The Flasher ARM is currently not in office, I'll update this thread once I get it. Thank you for you time, Fred
-
Thanks Michael, I just sent the correct hex file to support_flasher@segger.com. Can you tell me if you see any problems? Again, my issue only happens on a device that has never been programmed. If a device has been programmed once, then there is no problem. Thank you, Fred
-
Hi Michael, Here is the project file and hex. I used another hex file than our code, please tell me if the original code is needed.
-
Hi Michael, any update on this?
-
Hi Michael, Thanks for answering. It has to be on a device that has never been programmed. After having been programmed once, either by the Flasher ARM or by a Miniprog3, there is no problem in standalone. Yes, doing a power cycle manually does not change the behavior. Do you have an email so I can send you the project-file? Fred
-
Hi, We use the Flasher ARM in standalone mode in production for Cypress' CYBLE-022001-00. Right now, the Flasher can only work through JFlash, not in standalone mode. In standalone, the red LED lights up when I press the "Start" button, whereas everything goes smoothly with JFlash. I'm using JFlash v6.40, and the firmware in the Flasher is up-to-date with that version (accepted the firmware upgrade prompt when opening JFlash). I clicked "Download config & data file to Flasher" with success. What…
-
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 …
-
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 lo…
-
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 Commande…
-
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 th…