issue about hex file size

RE: issue about hex file size

Hieu — Thu, 01 Jun 2023 13:43:53 GMT

Hi Hannibal,

Our engineer looked quickly at the symptoms and think maybe imgtool.py is not working correctly. However, a deeper investigation cannot be scheduled at the moment.

I have made sure to put this issue into our internal tracking so that it will be worked on. However, I cannot comment on when a fix will be available.

If this issue is critical for you, I can connect you with a Regional Sales Manager to discuss further. Otherwise, I will try to update you here when the issue is fixed.

Our apologies for the inconvenience.

Best regards,

Hieu

RE: issue about hex file size

Hannibalhz — Thu, 01 Jun 2023 02:41:18 GMT

Dear Hieu

Thank you for your best supprts, I‘m going to expect your good news.

Best regards,

Hannibal

RE: issue about hex file size

Hieu — Wed, 31 May 2023 15:43:52 GMT

Hi Hannibal,

I reproduced the issue. Let me discuss with our engineers on this, and I will let you know if there are any updates.

Best regards,

Hieu

RE: issue about hex file size

Hieu — Fri, 26 May 2023 15:02:09 GMT

Hi Hannibal,

I am back, but I am still progressing through my backlog and could not get to your question yet. Please know that I am still around and will try to look into the issue within the next two working days.

I am sorry for the inconvenience.

Best regards,

Hieu

RE: issue about hex file size

Hieu — Tue, 23 May 2023 09:26:14 GMT

Hi Hannibal,

Let me get to this once I return to office later this week.

BR,

Hieu

RE: issue about hex file size

Hannibalhz — Mon, 22 May 2023 10:41:30 GMT

Hi Hieu

Your mcuboot_primary_app region is too smal, the sign script will report an error. When the mcuboot_primary_app region size has 1K to 8K, it can build.

BR,

Hannibal

RE: issue about hex file size

Hieu — Tue, 16 May 2023 10:18:38 GMT

Hi Hannibal,

Are you certain you can build an image as big as the entire slot 0, including data in the pad region?

I just quickly ran a test and that is not possible:

See in the screenshot that the build system restricts my image size by the size of the mcuboot_primary_app region, which has already accounted for a pad area of 512 bytes.

On top of that, even though I have not used all the space in my image yet, the build system already failed because there is not enough space to sign the image.

Could you give me some steps to reproduce your observation from a sample?

By the way, I will be out of office and return next Wednesday, May 24. Please excuse some delay in further responses due to this. My apology for the inconvenience.

Hieu