Search Results

It seems that copying also the Connect.pex file stored in the %config directory is the solution. No matter which version of JFlash is used.

Dear Niklas, it works again but I cannot say why yet. I tried the JFlash 6.15c beta and I copied in the Flasher also the directory with the Connect.pex file. Now my colleague will try to find an official procedure in order to document it. In anycase one of these two variations is the solution. Hope this helps someone. Cheers, Davor

Hi Niklas, actually the Flasher Portable stop working. So I was wondering if the cable could be the issue source... we are checking it right now. A scheme would be highly appreciated. Thanks in advance, Davor PS: if this doesn't work we should try with a test SW. We just received 5 new Flasher Portable and we are stucked.

Hi Niklas, thanks for your feedback. I'll try ASAP the test you describe. Sincerely, Davor

Hi Niklas, Yesterday after reading your post Quote: “[...] Standalone programming a secured device (0x040C set to 0xFF) also works. [...] ” I start wondering if secured device was the issue, so this morning I made some test. Result is that Flasher portable seems to work with 0x040C set to 0xF7. Freescale datasheet says that 01b is unsecured and others combination are always secured and we choose 00b. Can you check if I'm right please? Due to the fact that we develop medical devices it would be n…

Hi Niklas, actually you are right: with unsecured device I'm able to program in standalone mode even without "Init steps" WDG disabling. We secure the chip by setting 0x040C to 0xF4. By this we disable freescale factory access and we secure the flash. In this case I'm not able to program the chip in standalone mode... for now with or without WDG disabling instructions. Regards, Davor

Niklas, yes. The devices are already programmed and we need to rework lots of them with a new SW release. Unlock and erase are needed in order to be able to program them again. Sincerely, Davor

Hi Niklas, I've implemented something that seems to work better, see attached project. However I'm able to use the flasher in standalone mode only if the chip is already erased. We work in security mode and a mass erase is necessary to reprogram the chip. Any suggestions please? Thanks, Davor

Hi Niklas, thanks for your answer. I understand what you are asking for but I find difficult to implement it. To disable the watchdog I shall reset COP control register (bit 2 and 3), how I can find more informations about how to do it in "Init steps"? Thanks in advance and regards, Davor

Hi, I have an issue with the Flasher Portable: I'm not able to use it in standalone mode, but it works well while connected to a PC. Hereafter the error: ERROR: Failed to download RAMCode. ERROR: Failed to prepare for programming. Failed to download RAMCode! SN: 1 – Failed Environment info: - Win 7 professional - J-Flash 6.14d (also tried v6.15c) - Flasher Portable - Target Cortex-M0 MKL16Z128VLH4R I've tried to configure the project in order to perform only programming operation (no erase, nor …