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.

Flashing firmware leads to fault isr

Other Parts Discussed in Thread: TM4C129XNCZAD

Hi,

I try to program a custom board (this has been working sometime back). I use TM4C129XNCZAD.

I use Tiva Launchpad as a debugger.

I try to flash the code. It doesnt reach main. This happens even with example programs.

It goes to fault isr directly.

What could be the issue ?

Best Regards

Vivek

  • I try to flash the code. It doesnt reach main. This happens even with example programs.

    You can set a breakpoint at the reset vector, which is the very first function to execute (or deselect "run to main" in the project debug settings). Stepping through the initialisation code should tell you where the problem is.

    Perhaps a wrong startup file ? (e.g. C and C++ programs usually require different startups).

    I am using Crossworks, and not CCS (as you presumably), so I can't go into detail here.

    BTW, more information about your toolchain and involved code is probably helpful...

     

  • Vivek Gopalakrishnan said:
    I try to program a custom board (this has been working sometime back).

    That's an important statement - is it not?  Were you organized & disciplined enough to "save" that program which is reported as having worked (sometime back?)  If so - and if your IDE settings have not changed - should not a simple "reload" of that past, working code be a high priority?  Such seems a worthwhile (rather obvious) first effort.

    You speak to a "custom board" - does only one board exist?  And - is the one you're now using - the same as the one which had worked?  (such info not readily available - your brief post)

    The set-up of the IDE often proves too complex/challenging.   It's been proven that your use of "known good" factory programs - which employ the proper, factory selected IDE settings - yields the best chance of success...

  • cb1_mobile said:
    The set-up of the IDE often proves too complex/challenging.   It's been proven that your use of "known good" factory programs - which employ the proper, factory selected IDE settings - yields the best chance of success.

     Hi CB1, I am scared from how and where this question come... So is this firm working in a so worst environment or is an FAE left alone to a complex job in a dispersed country?

     Is quality of future at risk to drop so low? Is this firm trying to leave support to user of  product?

     Is the time of splitting beginner - advanced level this forum? I am reading it but all question come down to sub beginner level..... I wish to learn about production problem, about silicon errata not to be a nursery of screaming arduino like occasional hobby user!!!

     If arduino was an interesting market it is not an excuse to drop professional level into hobby screamer!

  • Roberto Romano said:
    I am scared from how and where this question come...

    That would make two of us, friend Roberto. 

    Normal to expect that "insider info" circulates - quickly/comprehensively aids when vendor-class, "crashes/burns!"

    Yet fear not Roberto - forum shortly receives "much needed" name change. (and all the delights which it likely brings...)

    Your suggestions - my past, detailed, "Poster's guide" - kicked to curb - yet time/effort/funds "front/center" for such, "non-essential."  (nary a nickel available to (properly) attend to festering sore that is PF0/PD7 - launchpad 0-ohm Rs)  But "name change" (yes name change!) - let's get right on that boyz!

    Vendor lacks imagination - clearly your, "Nursery of screaming, arduino like, occasional hobby user!!!" deserves, "nom du jour!"

  • Hello cb1, Roberto,

    For us even an "insider" is a customer when they are doing a new project with devices not familiar. And they run into an issue that maybe forum would benefit as well, so it makes a good idea to add this to the forum...

    Regards

    Amit

  • Hello Amit,

    Yes most of that is true - but one expects vendor class NOT to, "do a new project w/unfamiliar device - especially when that device is that vendor's!"  (seriously - how strange that...)

    Any review of this thread reveals sound guidance - supplied quickly by this reporter - thus far to silence.  (appears both device (MCU) and urgency/responsiveness are "unfamiliar" to this poster...unless he's "renaming" the forum...)

  • Back to the original question... <grins>

    Vivek, what kind of fault ISR are you getting into?  Do you mean the Hard Fault (0x000.000C) or Bus Fault (0x0000.0014) or other fault?  What is the value of the FAULTSTAT register or other relevant registers that may give a clue?

  • All,

    I intended to post this in an internal forum.

    I was also browsing other e2e posts.

    By mistake i had posted this in forum.

    Apologize for the inconvenience.

    -Vivek

  • Vivek Gopalakrishnan said:

    I intended to post this in an internal forum.

    I was also browsing other e2e posts.

    By mistake i had posted this in forum.

     Internal or external faulting professional form and identification pattern is not a simple fault. Sometimes silence is better than double fault.

     OBLIVION CPU HALTED!!!!