RM57L843: HalCoGen unable to set MPU region to NORMAL_OIWTNOWA_SHARED

Hi Danilo,

I started to be working on your issue and i will get back to you soon.

--
Thanks & Regards,
Jagadish.

Hi Danilo,

Customer right about this 

I have to check this with internal team for plan of action.

--
Thanks & Regards,
Jagadish.

Hi Jagadish,

Thank you for your response. Do you have any update regarding this issue?

Regards,

Danilo

Hi Danilo,

The dependency internal team is on leave, i will let you know the update as soon as possible.

--

Thanks & Regards,
Jagadish.

Hi Danilo,

I discussed but didn't get response yet from internal team, i will update you as soon as possible.

--

Thanks & Regards,
Jagadish.

Hi Jagadish,

We will be waiting for your update.

Regards,

Danilo

Hi Jagadish,

Our customer would like to know when is the expected release of the next version of HALCoGen.

Regards,

Danilo

Hi Danilo,

There is no official plan for next release, i will let you know if it is planned in future.

--

Thanks & Regards,
Jagadish.

Hi Jagadish,

Please see our customer's comment.

So, in other words TI is aware that HALCoGen, which is required to build software for RM57L (and possibly other MCUs) has bug which is not easy to spot and not easy to workaround and TI is not willing to fixing and releasing it?

If HALCoGen is effectively abandoned I would strongly suggest to improve workflow for developing software for TI's MCU to not required HALCoGen and release HAL libraries as non-templated source code which can be used directly

Regards,

Danilo

Hi Danilo,

Danilo A. said:

So, in other words TI is aware that HALCoGen, which is required to build software for RM57L (and possibly other MCUs) has bug which is not easy to spot and not easy to workaround and TI is not willing to fixing and releasing it?

Definitely there will be a HALCoGen refreshment and management about to planning that, but the date is not yet decided. And the issue in this thread is not a critical one to rectify immediately. So, this will be considered in our next release of HALCoGen.

--

Thanks & Regards,
Jagadish.

Hi Jagadish,

Please see our customer's response.

Understood, however any estimate for next release of HALCoGen would be appreciated given that it has many years since latest.

In the meantime I believe that issue such this one should be included in Known issues section of HALCoGen's release notes.

Regards,

Danilo

Hi Jagadish,

I just received this email from our customer.

I just checked Release notes for HALCoGen and this issue is still not listed in known issues section. Document is dated as 'October 2019'

Regards,

Danilo

Hi Danilo,

Yes, it is not a known issue, and it is found out in this thread only. And as i told you, it is considered for next release of HALCoGen.

--

Thanks & Regards,
Jagadish.

Hi Jagadish,

Please see our customer's feedback.

I understand that. I also understand that it might be some time before fixed version of HALCoGen is release. What I don't understand is why Release notes is not updated with this known issue.

To show you why I'm so persistant in this matter:
I was fighting with RM57L memory access via EMIF for three (!) weeks. Trying different EMIF settings, different clock settings, different MPU settings. Each time I got confusing results I checked errata for HALCoGen (release notes), errata for RM57L and none of these places suggested anything related to what I was doing. In despair I started looking into HALCoGen generated code, it's templates, configuration files and found this issue. It didn't solved my problems immediately but things started to make more sense. If this is issue was listed in Known issues it would save my days of debugging.

I get it, I was unlucky to be first one to find this issue but, please, update Known issues to someone else will not have to go through the same process.

Regards,

Danilo