Other Parts Discussed in Thread: HALCOGEN
Hello,
What are the known issues with HALCoGen v04.07.01?
Note that the information on the page has not been updated.
--thx
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello,
What are the known issues with HALCoGen v04.07.01?
Note that the information on the page has not been updated.
--thx
Hello Miro,
I need up-to-date information about known issues with HALCoGen. This is a crucial part of due diligence for our functional safety development process.
Jiri Janacek described this kind of need quite well back in 2015, so I'll refer you to Jiri's explanation (note that I am not affiliated with Jiri):
https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/442440/1633204#1633204
Back at that time, Prathap agreed to maintain an up-to-date table of known HALCoGen issues in your wiki:
https://e2e.ti.com/support/microcontrollers/hercules/f/312/p/442440/1647524#1647524
This is the same wiki page that is referred to in the release notes for v04.07.01:
Current details of the Device wise Software Maturity Level and the Bug list can be found in the HALCoGen WIKI Page http://processors.wiki.ti.com/index.php/HALCoGen
I appreciate that TI is phasing out the wiki, and I imagine that updating it is inconvenient. For our needs, it is immaterial whether the information is provided on the wiki or via some other means. Providing read-only access to your tracking database would be an effective way to do this.
Regardless of whatever your long term solution for maintaining HALCoGen is, however, I have an immediate need today to perform an analysis of the 3rd party components included in our safety-related firmware.
Can you please give us up-to-date information about the current known issues for HALCoGen?
--thx
This HALCoGen update is not yet out, correct? What is the anticipated timing of the release?
Note that while we will certainly appreciate having a temporarily-up-to-date list of the current known issues, this will not address our safety process's need on an ongoing basis for tracking the known information about 3rd-party code we're incorporating into our safety-related firmware.
How will we be able to track this information in the future?
--thx
Hello,
We are now working on an updated "release notes" document that includes a detailed description of all known issues with the version 4.07.01 of HALCoGen. This document is currently under review internally and is planned to be available online by the 20th of September.
Regards,
Sunil
I have sent you a "Friend request", which would allow me to share information with you that is not ready for public disclosure yet, such as the list of known issues that is being compiled.
Please accept the request, so I can send you the WIP list.
Regards, Sunil
Hello,
I assume you made a contact with Sunil and information needed is shared with you. That is why I am going to close this thread for. If you need further assistance you can reopen it with writing at the end or you can open new thread.