I am using two FLASHER ARM in my system. Both are driven via JFlash Command Line 5.12e with batch files like this:
start /min /wait "JFlashSPI" %1 -openprj%2 -open%3,0x00000000 -usb%4 -exit
The -usb option is used to select which FLASHER we are wanting to drive. When the FLASHER are connected to their devices (NOR FLASH Memory in this particular case), all is fine. However, if the NOR FLASH device is bad, or not powered or the power is removed from the NOR FLASH during the programmation period, the pop-up to select which Emulator to connect to pops up and wait for a manual input on the window.
In that case, I would want the JFlash to trigger an error and exit with no manual operation ... which is the purpose of using the JFlash Command Line interface.
Is that a limitation in the software? What should I do to counter this?
Thanks
Mathieu
start /min /wait "JFlashSPI" %1 -openprj%2 -open%3,0x00000000 -usb%4 -exit
The -usb option is used to select which FLASHER we are wanting to drive. When the FLASHER are connected to their devices (NOR FLASH Memory in this particular case), all is fine. However, if the NOR FLASH device is bad, or not powered or the power is removed from the NOR FLASH during the programmation period, the pop-up to select which Emulator to connect to pops up and wait for a manual input on the window.
In that case, I would want the JFlash to trigger an error and exit with no manual operation ... which is the purpose of using the JFlash Command Line interface.
Is that a limitation in the software? What should I do to counter this?
Thanks
Mathieu
The post was edited 1 time, last by mmassic ().