• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 766 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.

28335 No longer starts from power-on but works fine from Reset in the debugger

Johnathan Vail
Prodigy 200 points


I am stymied -- I used to have my downloader working fine and now it isn't working.  The main problem is if I do a RESET with the debugger (the "chip" icon) and then run it works fine.  No problem.  But I cannot start from power on.  However, an older version of my code does work from power on.  So something changed but I can't find out what and I can't seem to debug it from power-on without the debugger.

( I am sure it is something simple that changed. I have 2 months of changes before I noticed the problem, I have already diffed everything I thought could cause this)

Any ideas?  What happens at power-on that is different from the RESET in the debugger?  I have my vector at 0x33fff6. 

Another problem is my software induced watchdog reset is no longer working either.  If I jump to the vector instead it does work.

It kind of indicates there is something missing from an actual hardware reset and running from the vector.  What is it?

thanks!

jv

  • 0
    Guru 192875 points

    Hi Johnathan,

    Are you sure that your code is running via Flash and not RAM? Because such kind of behavior will be observed if the code is running from RAM!

    Regards,

    Gautam 

  • 0
    Guru 20525 points

    Hello Johnathan! (Hi Gautam!)

    Perhaps you have missed CodeStartBranch.asm - file at new project version.

    Regards,

    Igor 

  • 0 in reply to Igor Gorbachev
    Prodigy 200 points

    Hello Igor and Guatam,

    Thank you for the reply.  That isn't it.  I have 

    BEGIN 0033fff6 00000002 00000002 00000000 RWIX

    which I think is codestartbranch.asm ?  I don't have it in my project but I think it gets linked in with "Boot from FLASH" option from BIOS?  Anyway, there is code here and I can trace it with the debugger through a breakpoint here if I use the debugger chip reset.  The code works fine and does run from flash (I have a an easy way to tell from my application).  

    Also as I mentioned I had an older version of my code that does run from a hardware reset either from power-on or from watchdog.  Somehow now both my watchdog reset and the external power-on reset (and a wire jumper reset) no longer work with this version and I can't see what is different.  My theory is it is something very easy that broke but since I can't use the debugger I am at a loss to see what it is.

    jv

  • 0 in reply to Johnathan Vail
    Guru 20525 points

    Hi!

    Well, if you are so sure that your version should work without a file СodeStartBranch.asm then please refer to 0876.TI_Running_from_Flash_spra958l.pdf. Maybe I don't understand something.

    Regards,

    Igor

  • 0 in reply to Igor Gorbachev
    Prodigy 200 points

    It could be me that is misunderstanding....

    I am using SYS/BIOS with Boot from FLASH enabled which I believe does the same thing that the .asm file does.

  • 0 in reply to Johnathan Vail
    Guru 20525 points

    Hi!

    Maybe...But using SYS/BIOS does not affect. Solid Confidence should be based on practical results. If the result is negative now, I would prefer to reconfigure project and to apply CodeStartBranch. At least when nothing works the better way to refer to standard manual.

    Regards,

    Igor 

  • 0 in reply to Igor Gorbachev
    Prodigy 200 points

    Thanks Igor, 

    It is a good idea and I have verified the BEGIN branch is there with BIOS as it would be with codestartbranch.asm explicitly linked.

    I did trace through a little more and found the failure after a watchdog reset ending up at:

     00309c30    00000019                       : exit.obj (.text)

    in an infinite loop.

    I traced it some and it seems to go into BIOS and something then is wrong.  What could cause it to get to exit?  At least this is making more sense as to what is wrong.