Search Results

Hello Mike, you can do so. Therefore you need to add several commands in the exit step of your J-Flash project. Best regards, MichaelF

Hello Mike, 16 images is the correct answer, which you can add to the ini-file and select by the buttons. You can even load more onto the device. Best Regards, Michael

Dear Johan, what is the error message of the Flasher? Does the error also occur if you use the latest JFlash version 6.70? Can you provide us the JFlash project file (*.jflash)? Best regards, Michael

Hi Bjarne, many thanks for the feedback. --- CASE CLOSED --- Best regards, Michael

Hi Bjarne, you could split the EEPROM data into 2 part and apply e.g. 4 patch to the first part and 2 two the second. Best regards, Michael

Hello Bjarne, the Flasher programs only one line per target device. If you want to apply more than one patch to a target all patches must be in one line. Or you use the "#auto patch" command and add the patch data after the command. Best regards, Michael

Hi Bjarne, you can use the auto patch command for that. The syntax is described in the manual. Please note the data file must contain these areas at least filled with dummy data. Best regards, Michael

Hello Bjarne, the lines SDA, SDL, GND, VTref need to be connected. The 24LC512, you mentioned in all posts before, has 128 bytes / page. In case of the 24LC025 the page size should be 16 bytes and you should use the 24C02 device in the Universal Flash Loader project. The ASCII command protocol is defined without the LF and only the CR at the end of the line. Most terminal can switch to CR mode only. Best regards, Michael

Hi Bjarne, We checked your file. We found two points: 1) the page size should be 128 byte as the spec says. But should not be the root cause. 2) the error, reported in the last post, looks like the write protect pin is set to protected. Can you check that on your hardware? Best regards, Michael

Dear Jacoben, the main differences between the Flasher ARM and the Flasher Portable PLUS is in addition to the display: -the Flasher Portable PLUS cannot be automated in standalone mode and -the Flasher ARM and Flasher Portable PLUS support a difference list of devices. By the way you can also store multiple images on the Flasher ARM. So both device may fit your requirements. Best regards, Michael Fuhs

Hi Yves, the Flasher Portable was replaced, as you know, by the Flasher Portable PLUS more than 2 years ago. There are some improvements made with the latest JFlash version which were not back ported to the Flasher Portable. The latest version for the Flasher Portable is from 23th Sep 2015. We would recommend to upgrade the Flashers to Flasher Portable PLUS. You may check our trade-in program for that. see: segger.com/purchase/trade-in-program/. Best regards, Michael Fuhs

Hello Denis, the Flashers do unsecure the device in stand alone mode without any asking to the customer. So you do not need to do anything additional for this. Bet regards, Michael Fuhs

Hello Phil, there is an internal log file. If you mount the Flasher as MSD device, you can open the Flasher.log. To do so, press the PRG button while you plug in the USB cable. In addition you can record the outputs on the RS232 (9600 baud, 8N1) connector or use the Telnet connection on the LAN interface. For further support we would need the output of the terminal, the device name and the JFlash-Project file (*.jflash). Best regards, Michael

Hi, we will consider, if that is a useful enhancement for the Flasher device. Best regards, Michael Fuhs

Hi, no there no currently no command to read the button state. May be you can use the "#RESULT" command to get the current state of the Flasher. In idle the answer is "#RESULT:READY", during programming it changes "#RESULT:INIT", "#RESULT:CONNECTING", ... "#RESULT:VERIFY". Best regards, Michael Fuhs

Hi Fred, we tried to program your file which works. But our modules had been programmed several times before. Do you have a custom hardware or an eval board? Could you send us a hardware for investigation? Best regards, Michael Fuhs

Hi Fred, I received your files. We will check it. Best regards, Michael Fuhs

Hi Fred, I checked your JFlash project file. That looks fine and I can program test data into the chip with it. The data file seems to be wrong. It includes some data which do not fit into the Flash at address 0x9060000. That is the option byte for the Flash Protection. The value in your test file says it is not secured. So you could remove and it will work. Securing this Chip is not supported out of the box, yet. Best regards, Michael Fuhs

Hi Fred, sorry too busy the last days. Of course, you may send it to support_flasher@segger.com Best regards, Michael Fuhs

Hi Fred, I tried to reproduce your issue with our CYBLE-022001-00 eval board. I cannot see the described behavior. When can you observe this behavior? Is it reproducable when you do a power cycle on the chip and try to program it again in standalone mode? Can you reprogram a already programmed device after a power cycle? Can you send us your jflash-project file, too? Best regards, Michael Fuhs