To update the operating system from an SD card, a special SD card (an SD Boot card) needs to be made that contains an OS image in a partition outside of the file system (an SD card image). This partition will be hidden when viewing the SD card but can be seen using Windows’ Disk Manager as an unallocated partition. When the system starts with an SD Boot card, the OS image is loaded from that card and not from NAND flash.
Warning: Do not confuse an NK.bin file in the SD Boot card’s file system with the OS image that is running. The OS image that runs will not show up as a file, but as a non-allocated area when viewed by Windows’ Disk Management tool. The NK.bin file contains the OS that will be installed on the NAND flash. |
To update the bootloader and OS image, you need to run a program called ProdFlasher.exe on the system. It will flash both the bootloader image and the OS image. This will take less than 3 minutes, so if there is no color display, please wait and confirm in the OSLOG-file that the flashing was successful.
It is highly recommended to use a color display when updating OS and EBOOT. There is a risk that you might need to update the Bootloader with JTAG, if the terminal is rebooted too early.
Warning: The SD Boot card should never be left in the terminal during normal operation. The OS on the SD Boot card cannot be updated remotely and does not contain certain security modules required by PA-DSS. Please mark these cards clearly, so no mix-up will occur. |
If the terminal doesn’t start at all and only shows a blank screen than the bootloader is corrupt and you have to re-install it using JLINK.
If the terminal shows the splash screen on start up but does not continue from there than the OS is corrupt. You can re-run the SC Boot card installation again.