• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 31 subscribers
  • Views 575 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Needed for ALL ESM channels: Blocking behavior in case more than one flag for an ESM channel exists.

oliver.gruendonner
Intellectual 830 points
Other Parts Discussed in Thread: TMS570LS3137

Hi.

My question is regarding the TMS570LS3137.

My question is already stated in the discussion http://e2e.ti.com/support/microcontrollers/hercules/f/312/p/304060/1060473.aspx, title "Blocking behavior in case more than one flag for an ESM channel exists.", "Posted by Oliver Gr??ndonner on Nov 19 2013 07:31 AM". See especially the note at the end of the posting, i.e.:
    "... NOTE: These are only two examples. But the question regarding the blocking behavior raises for ALL ESM channels for which there are two or more flags for one and the same ESM channel."
So if already the above discussion was opened, why I open a new discussion? Cause in the above discussion only the behaviour of ESM Group1, Channel 2, DMA - MPU, was discussed. But as stated in the note above: I need this inforamation for ALL ESM channels. And in "Posted by Anthony F. Seely on Nov 20 2013 18:12 PM" (of the above linked discussion) is stated
    "The MPU in the DMA is unique so I would not regard this as a general answer for all IPs on the device. They need to be asked on a case-by-case basis. ..."

So I would ask you to provide the blocking behaviour for ALL ESM channels for which there are two or more flags for one and the same ESM channel.

Thank you and regards
Oliver.

  • 0
    TI__Mastermind 23000 points

    Hello Oliver,

    Thank you for the feedback.  We will review the feedback when developing future architectures.

    Best Regards,

    Karl 

  • 0 in reply to KGreb
    TI__Guru 68920 points

    Hi Olvier,

    I talked to Karl about this post.    Karl's answer is to a part of your post making suggestions for future devices.

    I'm answering now the request for the information on the current product.   I can see where this information is needed.  We plan to talk to our manager about how to close this documentation gap in our next meeting - since it's a fairly large project to get the information for each IP.   But it seems like we do have a documention gap that needs to be filled.

    Thanks ahead for your patience on this one.

     

  • 0 in reply to Anthony F. Seely
    Intellectual 830 points

    Anthony,

    thank you for your insight, that there is important (or at least important for safety critical projects) information missing in the documentation. Since our project is already in a close to final state, we don't want to make big changes. And with every additional day, we want to do less changes. So I would ask you, if it's possible, to estimate till when the missing doc. information could be available. I don't want to have a concrete date, I only want to know if it would be possible for you to provide such information still in Nov or Dec/2013, or not before Jan/2014? So with this information we would have a better ability for project planning.

    Thank you and regards

    Oliver.

  • 0 in reply to oliver.gruendonner
    TI__Guru 68920 points

    Oliver,

    Understand and this is a reasonable request.  I don't have an estimate yet, we need to have a meeting on how to divide and conquer this as a team and get back to you.  Dec 13 does seem tight especially w. Holidays.

    If this helps a little - a few of us met yesterday to get the background and there is a 'rule of thumb' in the sense that if the signal is documented as an "Interrupt" but is routed ot the ESM then in the IP it will be a level output and have the potential of the blocking problem given that the ESM is edge sensitive on inputs.    This is because in some cases the IPs had error interrupts before the ESM module was developed and these interrupts were connected to ESM rather than developing new outputs and making IP changes.  DMA falls into this category.

    Whereas if the module has been documented as having an Error output without the word interrupt in the description - this is most likely an edge sensitive output.

    Of course this is not sufficient information but maybe it can be used to make educated guesses until we have confirmed edge v.s. level with the hope of minimizing rework.

    Will get back to you next week on an estimate

  • 0 in reply to Anthony F. Seely
    Intellectual 830 points

    Hi Anthony.

    Any news regarding this topic?

    Regards

    Oliver.

  • 0 in reply to oliver.gruendonner
    Intellectual 830 points

    Hi.

    Any news regarding this topic?

    Regards

    Oliver.

  • 0 in reply to oliver.gruendonner
    TI__Guru 68920 points

    Hi Oliver,

    No updates on this post yet.  Might be best to communicate through Herbert on this rather than forum since it will take some time.

    On your other item - the eFUSE question;  I do think we can close this one near term;  I mainly need to round up the few experts and review my analysis w. them.   Unfortunately I just haven't had a chance to do this the past few days;  been sick and trying to avoid people ;)

  • 0 in reply to Anthony F. Seely
    Intellectual 830 points

    Hi.

    Was clarified through local TI contact.

    Regards

    Oliver.