author | Stephen Molfetta <sjmolfetta@ti.com> | |
Thu, 29 Oct 2020 03:55:43 +0000 (22:55 -0500) | ||
committer | Sivaraj R <sivaraj@ti.com> | |
Mon, 2 Nov 2020 04:54:05 +0000 (22:54 -0600) | ||
commit | b7b8c220e934b4f51269cce1b1c68161571912a8 | |
tree | af4f5bf908d3f3f4c57087e07c498cc745970707 | tree | snapshot (tar.xz tar.gz zip) |
parent | c5b0909886f5a916c468a795b4394299e6097700 | commit | diff |
sciclient: Update RM boardcfg after TIFS processing
In HS builds using unoptimized/development boot flows, RM boardcfg will
have a certificate prefix. TIFS will strip the certificate after
authentication and copy the boardcfg back in-place.
When returning for rm_pm_hal processing, adjustments to the RM boardcfg
request must be made:
- Invalidate the cache
- Adjust the length of the boardcfg request to compensate for the
missing certificate
- If the certificate is not stripped (which would be the case if the
signed RM boardcfg is sent a second time from an application), adjust
the boardcfg pointer to pick up from the offset of the certificate
Signed-off-by: Stephen Molfetta <sjmolfetta@ti.com>
In HS builds using unoptimized/development boot flows, RM boardcfg will
have a certificate prefix. TIFS will strip the certificate after
authentication and copy the boardcfg back in-place.
When returning for rm_pm_hal processing, adjustments to the RM boardcfg
request must be made:
- Invalidate the cache
- Adjust the length of the boardcfg request to compensate for the
missing certificate
- If the certificate is not stripped (which would be the case if the
signed RM boardcfg is sent a second time from an application), adjust
the boardcfg pointer to pick up from the offset of the certificate
Signed-off-by: Stephen Molfetta <sjmolfetta@ti.com>
packages/ti/drv/sciclient/src/sciclient/sciclient_direct.c | diff | blob | history |