S32k358 Service HSE_APP_DEBUG_KEY_ATTR_ID returns HSE_SRV_RSP_NOT_ALLOWED

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32k358 Service HSE_APP_DEBUG_KEY_ATTR_ID returns HSE_SRV_RSP_NOT_ALLOWED

823 Views
hyunbeenkwon
Contributor I

Hi,

I want to write adkp in our software.

We are trying with nxp demo codes.

While source code tries program adkp, some tries return HSE_SRV_RSP_NOT_ALLOWED, and other tries return ok.

Tell me there is any other preconditions we don't know.

1. adkp shall be written in program block 1(whole source codes that related with writing adkp shall locate in program block 1)

2. during writing adkp, program block 0 shall be not accessed in any other cores

To solve 1, we moved whole source codes that are related with writing adkp to program block 1.

Also, to solve 2, we suspended another core job while writing adkp, and resume after writing adkp.

0 Kudos
Reply
2 Replies

769 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

Probably reason could be enabled data cache. Pay attention following thread, describing the same issue:

https://community.nxp.com/t5/S32K/HSE-ReadAdkp-returning-HSE-SRV-RSP-INVALID-ADDR/m-p/2264487

 

0 Kudos
Reply

787 Views
hyunbeenkwon
Contributor I

To add some details, we are using password, and static method.

Thus, neither adkp master method nor enableADKm is used.

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2293029%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ES32k358%20Service%20HSE_APP_DEBUG_KEY_ATTR_ID%20returns%20HSE_SRV_RSP_NOT_ALLOWED%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2293029%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI%20want%20to%20write%20adkp%20in%20our%20software.%3C%2FP%3E%3CP%3EWe%20are%20trying%20with%20nxp%20demo%20codes.%3C%2FP%3E%3CP%3EWhile%20source%20code%20tries%20program%20adkp%2C%20some%20tries%20return%26nbsp%3BHSE_SRV_RSP_NOT_ALLOWED%2C%20and%20other%20tries%20return%20ok.%3C%2FP%3E%3CP%3ETell%20me%20there%20is%20any%20other%20preconditions%20we%20don't%20know.%3C%2FP%3E%3CP%3E1.%20adkp%20shall%20be%20written%20in%20program%20block%201(whole%20source%20codes%20that%20related%20with%20writing%20adkp%20shall%20locate%20in%20program%20block%201)%3C%2FP%3E%3CP%3E2.%20during%20writing%20adkp%2C%20program%20block%200%20shall%20be%20not%20accessed%20in%20any%20other%20cores%3C%2FP%3E%3CP%3ETo%20solve%201%2C%20we%20moved%20whole%20source%20codes%20that%20are%20related%20with%20writing%20adkp%20to%20program%20block%201.%3C%2FP%3E%3CP%3EAlso%2C%20to%20solve%202%2C%20we%20suspended%20another%20core%20job%20while%20writing%20adkp%2C%20and%20resume%20after%20writing%20adkp.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2293425%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32k358%20Service%20HSE_APP_DEBUG_KEY_ATTR_ID%20returns%20HSE_SRV_RSP_NOT_ALLOWED%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2293425%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EProbably%20reason%20could%20be%20enabled%20data%20cache.%20Pay%20attention%20following%20thread%2C%20describing%20the%20same%20issue%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2FS32K%2FHSE-ReadAdkp-returning-HSE-SRV-RSP-INVALID-ADDR%2Fm-p%2F2264487%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Fcommunity.nxp.com%2Ft5%2FS32K%2FHSE-ReadAdkp-returning-HSE-SRV-RSP-INVALID-ADDR%2Fm-p%2F2264487%3C%2FA%3E%3C%2FP%3E%0A%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2293156%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32k358%20Service%20HSE_APP_DEBUG_KEY_ATTR_ID%20returns%20HSE_SRV_RSP_NOT_ALLOWED%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2293156%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3ETo%20add%20some%20details%2C%20we%20are%20using%20password%2C%20and%20static%20method.%3C%2FP%3E%3CP%3EThus%2C%20neither%20adkp%20master%20method%20nor%20enableADKm%20is%20used.%3C%2FP%3E%3C%2FLINGO-BODY%3E