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.
SPRZ412M omits mention of the '379D in *Table 3-2 Memories Impacted by Advisory* in section *Memory: Prefetching Beyond Valid Memory*. Can anyone provide a table for the F28379D?
Also, can someone provide further clarification on the note "code should not come within 8 words of the end of valid memory": does "code" mean "program" memory, "data" memory, or both?
Hello Ethan,
I will look into your question regarding whether this errata applies to the F28379D and what that information looks like.
Also, can someone provide further clarification on the note "code should not come within 8 words of the end of valid memory": does "code" mean "program" memory, "data" memory, or both?
If you read the 'Details' section of the erratum, it is discussing the C28x CPU instruction prefetches that occur as part of the pipeline. Code in the 'Workarounds' section is therefore referring to program code, as the CPU will do prefetches as part of the pipeline (accessing data is just accessing data at an address, so unless you read beyond the memory bounds you should be fine; you should be making sure your code is reading data within the proper bounds anyways, this erratum refers only to program code that is executing).
Best regards,
Omer Amir
Hello Ethan,
Can anyone provide a table for the F28379D?
I confirmed with the memory expert that the table should apply to the F28379D, since it shares the same memory map as the F28378D. I've made a note for the next time this document is updated.
Best regards,
Omer Amir
Thanks for confirmation that the table still applies, but it is still ambiguous as to which column should the `379D fall into: the left column (with the `378D) or the right column (with the '376D)?
Doh! After I posted my query, I realized that the logical answer is the left column.