==================================================================================================
FBL은 시스템 부팅 시 가장 처음 활성화되는 SW 모듈입니다. 업데이트를 처리하기 위한 루틴이 존재하고, 업데이트 시 CRC check나 SeedKey check와 같은 내부 인증 절차를 거치는데, 시스템에 사전 정의된 방식으로 업데이트 바이너리를 검사하고, 확인된 문제가 없다면 Flash 메모리에 업데이트 버전을 복사하게 됩니다. Flash 메모리에 쓰기가 끝나면 다시 한번 기록한 바이너리의 정합성 및 동일성 검사를 하고, 이상이 발견되지 않으면 FBL에서 어플리케이션으로 제어가 넘어가게 됩니다. Reprogramming 관련 FBL 프로세스는 2단계로 구분할 수 있는데, 때로는 명시적으로 별도의 처리 기능별 FBL로 나누어 구현하기도 합니다.
첫번째 번역
The FBL comes to SW modules to be activated by the very first at system booting. Being updates processing routines existed, with updates, going through the internal authentication procedures such as CRC check or SeedKey check, checking updates by predefined ways to a system, and without failures confirmed, comes to copy up the update version to the flash memory.
With the complete of writing on the flash memory, checking the consistency and identity of the written binary once again, without failures, controls pass over to an application from the FBL. The FBL process regarding Reprogramming is parted by 2 steps. Explicitly exceptional processing functions per FBL could be implemented from time to time.
기계 번역
The FBL is the first SW module to be activated when the system boots. Routines exist for processing updates, and internal authentication procedures, such as CRC check or SeedKey check, are performed to check the update binaries in a predefined manner on the system, and if there are no known problems, copy the update to Flash memory. After writing to Flash memory, the consistency and identity of the recorded binary are checked again, and if no abnormality is found, control is transferred from the FBL to the application. The FBL process related to reprogramming can be divided into two stages, sometimes explicitly divided into separate processing functional FBLs.