Dear friends at Segger,
Our Flasher Portable fails when trying to program a STM32F4 firmware which includes the Device.pex file (in its proper directory).
Notice that:
1. the FAIL LED turns on immediately, as soon as pressing the PROG button
2. the FLASHER.LOG just contains this generic error line: SN: 8014 - Failed
3. the same firmware (including the same .pex file) works fine on a Flasher Portable PLUS
4. if we remove the folder containing the .pex file, then the Flasher Portable too programs the target successfully
At point 4 we apparently found a solution. But I wonder if removing the .pex file is a safe thing to do. If not, what are the risks?
The firmware seems to have been loaded correctly, even without the .pex file on the Flasher Portable. But is it really OK?
Any idea about what could cause the problem?
Please find attached most of my files (except for the .dat firmware file).
Our Flasher Portable fails when trying to program a STM32F4 firmware which includes the Device.pex file (in its proper directory).
Notice that:
1. the FAIL LED turns on immediately, as soon as pressing the PROG button
2. the FLASHER.LOG just contains this generic error line: SN: 8014 - Failed
3. the same firmware (including the same .pex file) works fine on a Flasher Portable PLUS
![?(](https://forum.segger.com/wcf/images/smilies/confused.png)
4. if we remove the folder containing the .pex file, then the Flasher Portable too programs the target successfully
At point 4 we apparently found a solution. But I wonder if removing the .pex file is a safe thing to do. If not, what are the risks?
The firmware seems to have been loaded correctly, even without the .pex file on the Flasher Portable. But is it really OK?
Any idea about what could cause the problem?
Please find attached most of my files (except for the .dat firmware file).