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:sbl reboot
| BoxMatrix >> System >> sbl_reboot | @ 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 |
| Devices | Filesystems | Partitions | Sockets | Netlink | Pipes | Interfaces | Bridges | Ports | Events | Sources | Sinks | AVMIPC | Processes | Watchdogs | Memory | Slab | Vmalloc | ProcFS | SysFS | Research |
Procfs-Object
| Procfs-Object: | sbl_reboot - type File | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Location: | System >> Proc-Filesystem - Origin: AVM | ||||||
| Path: | /proc/avm | ||||||
| Properties: | Firmware: 7.29 - 7.58 - Kernel (perm): 4.4.271 (r), 4.4.60 (r) | ||||||
| Function: | Multi-EVA: SBL reboot status | ||||||
Goto: Examples - Dependencies - Model-Matrix - Help Supportdata2 - SMW-Browser
Details
sbl_reboot provides the reboot status of the currently booted Secondary Bootloader (SBL).
Possible values are:
sbl_reboot is provided by avm_tz.ko. Excerpt from the source:
/* The reset status from the dakota is hold in a register, but unfortunately * the second stage bootloader (sbl) saves the value into a memory location * and clears the register. * As we do not want to update the sbl in the field and not clearing the * reset status register might change the behavior of the trustzone, the * following code has to be used to retrieve the value. * Note: The sbl masks the 5th bit of the value, thus the retrieved * value differs from the one shown during bootup. * Retrieved value, shown value during bootup, known cause: * 0x00 (0x00) cold boot * 0x00 (0x10) reboot * 0x23 (0x33) secure watchdog reboot */ static uint32_t dakota_reset_status;
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
Examples
7520 fw 7.29 example:
root@fritz1:/var/mod/root# cat /proc/avm/sbl_reboot SBL reboot status: 0x0
Dependencies
Daily updated index of all dependencies of this object. Last update: GMT.
A ** in the Mod column marks info from Supportdata2 probes, which will always stay incomplete.
A - in the Mod column marks manual research, the Firmware then shows where the Object occurs, not the Relation.
| Relation | Typ | Object | Mod | Firmware | Info | Origin |
|---|---|---|---|---|---|---|
| 0 dependencies for this object | ||||||
Model-Matrix
Daily updated index of the presence, path and size of this object for each model. Last update: 2024-12-30 05:07 GMT.
Showing all models using this object. Click any column header (click-wait-click) to sort the list by the respective data.
The (main/scrpn/boot/arm/prx/atom/rtl) label in the Model column shows which CPU is meant for Multi-Linux models.
Note that this list comes from Supportdata2 probes, which can have arbitrary settings and come from different firmware versions.
It doesn't say much if a model is not listed here. It may be a missing supportdata2 file or just a disabled feature.
| Model | Firmware | Path | Kernel (perm) |
|---|---|---|---|
| FRITZ!Box 4060 | 7.30 - 7.39 | /proc/avm | 4.4.271 (r), 4.4.60 (r) |
| FRITZ!Box 5590 Fiber (main) | 7.29 | /proc/avm | 4.4.60 (r) |
| FRITZ!Box 6850 LTE | 7.39 | /proc/avm | 4.4.60 (r) |
| FRITZ!Box 6850 5G | 7.39 | /proc/avm | 4.4.60 (r) |
| FRITZ!Box 7520 | 7.29 - 7.50 | /proc/avm | 4.4.271 (r), 4.4.60 (r) |
| FRITZ!Box 7520 v2 | 7.31 | /proc/avm | 4.4.60 (r) |
| FRITZ!Box 7530 | 7.39 | /proc/avm | 4.4.271 (r) |
| FRITZ!Smart Gateway | 7.58 | /proc/avm | 4.4.271 (r) |
| FRITZ!Repeater 6000 | 7.29 - 7.39 | /proc/avm | 4.4.60 (r) |
| 9 models use this object | |||
Help Supportdata2
The data in this article is incomplete since it was manually collected using the Supportdata2 project.
Unlike the Supportdata-Probes which have been collected for years Supportdata2 is brand new and only has a few probes.
If you have access to a shell then please help to extend the Supportdata2 collection to improve this data.
It's easy and it's done in minutes. Please send created data as an Email attachment to the address listed here. Thanks!
