psa_ps_set() returning -135 ERROR

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Mon, 09 Sep 2024 10:37:16 GMT

Hi,

[quote user="RAGHAV_M"]Before i tried with struct i changed that to union due to size issue[/quote]

I see. Union is not what you want here. It has it's uses in C, but not here.

[quote user="RAGHAV_M"]what you exactly mean by spliting do i need to split buffer or have other partition of 2 KB[/quote]

The maximum size you can write is 4024 byte. So if you need to write more (like 4096), you need to split that in two (or more) chunks. So for instance, that could be one 4024 buffer and the remaining 72 bytes in another buffer, or y ou can split in a different way. The main thing is that you cannot store an asset larger than 4024 bytes. If this is difficult, what about just making two 2048 byte buffers and memcypy into thouse, and store those? Then when you read the two buffers, you can memcpy into a larger buffer again if needed.

Note that in order to be able to store 4024 you need to allocate some larger buffers in TF-M, using CONFIG_TFM_CRYPTO_IOVEC_BUFFER_SIZE. So when I tested, I used these additional configs:

CONFIG_TFM_PS_MAX_ASSET_SIZE=4024
CONFIG_TFM_CRYPTO_IOVEC_BUFFER_SIZE=16384

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Fri, 06 Sep 2024 08:57:35 GMT

Before i tried with struct i changed that to union due to size issue, what you exactly mean by spliting do i need to split buffer or have other partition of 2 KB

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Fri, 06 Sep 2024 08:42:02 GMT

Hi,

Here you are calling psa_ps_set() with an asset which is too large and cannot work. I suggest you split it in two.

Another unrelated issue is the union you have of buf and len (response_info_t). Note that in C, all members of the union are in the same address space, so it is difficult to see what the intention here was. Perhaps this should have been a struct?

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Fri, 06 Sep 2024 07:57:34 GMT

Einar Thorsrud for your reference i am sending snippet if you find any mistake let me know

#define RESP_INFO_BUF_SZ = 4096
psa_storage_uid_t uid2 = UID_RESPONSE_INFO_DATABASE;
	psa_storage_create_flags_t uid2_flag = PSA_STORAGE_FLAG_NONE;
    psa_status_t status = PSA_ERROR_DOES_NOT_EXIST;
    size_t read_len = 0;
    
typedef union {
    uint8_t buf[RESP_INFO_BUF_SZ];
    uint16_t len;

} response_info_t;

response_info_t response_info;

memset((uint8_t *)&response_info, 0, sizeof(response_info));	
for(uint8_t off = 0; off < 100; off++){
            response_info.buf[off] = off;
}

status = psa_ps_set(uid2,  sizeof(response_info), (uint8_t *)&response_info, uid2_flag);

if (status != PSA_SUCCESS) {
         return APP_INIT_ERROR;
}

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Fri, 06 Sep 2024 07:43:39 GMT

In my case i have already other partition which is 1Kb of size i am trying add other partition with different UID which i need 4 KB buffer size and if u are saying split that buffer size that i'll try.

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Fri, 06 Sep 2024 07:38:49 GMT

Hi,

There was a typo in my previosu reply that made it unclear. I ment to say that it will not be possible to store your 4 kB data as one asset, so you need to split it up. Can you try setting CONFIG_TFM_PS_MAX_ASSET_SIZE to a lower number (could also be 2100) and split your data in two 2 kB assets that you write? That would work around the limitation.

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Fri, 06 Sep 2024 07:24:53 GMT

HI Einar Thorsrud

sorry I didn't get you can you explain in detail

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Thu, 05 Sep 2024 14:18:59 GMT

How big chunks are you tryign to write now? What if you set the CONFIG_TFM_PS_MAX_ASSET_SIZE to say 2500 and devide your 4k asset in two 2k pieces and write those?

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Thu, 05 Sep 2024 13:05:45 GMT

Hi Einar Thorsrud

thanks for the reply

if I do like this it shows error -132 i.e PSA_ERROR_GENERIC_ERROR

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Thu, 05 Sep 2024 10:29:45 GMT

The maximum asset size is lower than 4096 as the asset including additional metadata must be within a flash page, which is 4096 bytes. So the absolute maximum value you can set CONFIG_TFM_PS_MAX_ASSET_SIZE to is 4024.

So if you need to store more data you must split it up and store it as several assets.

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Wed, 04 Sep 2024 12:40:53 GMT

Hi thanks for the reply

I am using sdk v2.6.0

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Wed, 04 Sep 2024 12:39:57 GMT

Which SDK version are you using?

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Wed, 04 Sep 2024 09:26:26 GMT

Einar Thorsrud do you have any update regarding this issue.

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Tue, 03 Sep 2024 11:52:43 GMT

Thanks for the reply Einar Thorsrud

actually I tried it before only but it's not working.

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Tue, 03 Sep 2024 11:41:57 GMT

Hi,

You can configure a larger asset size with CONFIG_TFM_PS_MAX_ASSET_SIZE.

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Tue, 03 Sep 2024 09:29:16 GMT

Einar Thorsrud Could you please give me some update on this issue as soon as possible

RE: psa_ps_set() returning -135 ERROR

RAGHAV_M — Mon, 02 Sep 2024 13:42:00 GMT

Thanks for the response

can you please provide some suggestions to resolve this issue.

RE: psa_ps_set() returning -135 ERROR

Einar Thorsrud — Mon, 02 Sep 2024 13:39:53 GMT

Hi,

Return code -135 is PSA_ERROR_INVALID_ARGUMENT. I expect this si due to using a length larger than the maximum asset size.