If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:PBL
| BoxMatrix >> Lexicon >> Computer-Terms >> PBL | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Computer | FRITZ | I18N | Telephony | Smarthome | Internet | Protocols | Multimedia | Formats | Hardware | Software | Research |
Term
| Term: | PBL | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Short for: | Primary BootLoader | ||||||
| Location: | Lexicon >> Computer-Terms | ||||||
| Weblinks: | Wikipedia.int | ||||||
| Description: | First stage of the boot process on ARM based systems | ||||||
Goto: FRITZ!OS - SMW-Browser
Details
The PBL is the Primary Bootloader which executes the Secondary Bootloader (SBL).
It is part of the SecureBoot concept as used for Android and other modern ARM based systems.
The PBL is typically located on chip in the Boot-ROM (aka SecureCore) and is placed there by the chip manufacturer.
The SBL is a signed executable located on external storage and is customized by the device vendor.
The PBL searches for bootable media (flash), locates the SBL in it, validates its signature and executes it.
FRITZ!OS
In FRITZ!OS the PBL takes approx. the furst 0.3 seconds after powerup to locate, verify and launch the SBL.
Excerpt from a 7520v1 PBL / SBL Serial-Console log[1]:
Format: Log Type - Time(microsec) - Message - Optional Info Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic S - QC_IMAGE_VERSION_STRING=AVM_BOOT.BF.3.1.1 S - IMAGE_VARIANT_STRING=DAABANAZA S - OEM_IMAGE_VERSION_STRING=1204 S - Boot Config, 0x00000025 S - Reset status Config, 0x00000000 S - Core 0 Frequency, 0 MHz B - 261 - PBL, Start B - 1339 - bootable_media_detect_entry, Start B - 2612 - bootable_media_detect_success, Start B - 2626 - elf_loader_entry, Start B - 4044 - auth_hash_seg_entry, Start B - 5975 - auth_hash_seg_exit, Start B - 110185 - elf_segs_hash_verify_entry, Start B - 301613 - PBL, End B - 0 - SBL1, Start <snip>
See the SBL article for the full log.
Multi-EVA boot on Qualcomm-ARM:
- SoCs: Hawkeye, Alder, Miami, Dakota, Maple
- Lexicon: PBL, SBL, TrustZone, EVA
- Procfs: sbl_version, sbl_reboot, struct_version
- Procfs: sbl_fault_register, sbl_reset_debug, sbl_wdog_status, sbl_wonce
- Procfs: tz0_verified, tz0_version, tz1_verified, tz1_version
- Procfs: tz_boot_ack, tz_boot_index, tz_version
- Procfs: eva0_verified, eva0_version, eva1_verified, eva1_version
- Procfs: eva_boot_ack, eva_boot_index
- Firmware: sblupdate, tzupdate, urladerupdate
- Commands: tz_update
- Startup: E02-tz_update, cortexa9, cortexa9.service
- Partitions: GPT, alignto512, align_config_to_4mb, SBL1, SBL1_1, MIBIB
- Partitions: BOOTCONFIG, BOOTCONFIG1, QSEE, QSEE_1, DEVCFG, DEVCFG_1, RPM, RPM_1
- Partitions: CDT, CDT_1, APPSBL, APPSBL_1, CONFIG, CONFIG_1, TME, TME_1
- Kconfig: CONFIG_AVM_FASTIRQ, CONFIG_AVM_TZ_EXTENSIONS, CONFIG_QSEECOM
- Kernel: avm_sbl.ko, avm_tz.ko, qseecom.ko, ipq40xx_qseecom.ko
