This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Code Compiled, linked, downloaded but not running

Hi,
Do you have faced with this problem ? The USB debug adapter runs but the IDE debugger not. I can put breakpoint on the first line of the main but no break, no timer it generated too, when i stop running no stop on the code line executing.
It seems there is a problem just before the main call.

thx

Parents
  • I have three reasons for being careful with the use of initialized file-level variables. Basically for fast boot times and for high availability.

    1) In some situations, the power source may require extremely fast boot times or the reset may possibly be used as a kind of interrupt. Or the environment may be so noisy that it may affect the brownout logic, but requiring the system to recover fast enough that the reboot will not be noticed or at least harmful.

    2) Self-healing in case of memory corruption. With constant data protected in flash, and important variables being validated and/or regenerated, the probability of malfunction can be reduced.

    3) Variables initialized by the application are easier to group together into logical blocks and protected by checksums, or possibly redundantly stored.

Reply
  • I have three reasons for being careful with the use of initialized file-level variables. Basically for fast boot times and for high availability.

    1) In some situations, the power source may require extremely fast boot times or the reset may possibly be used as a kind of interrupt. Or the environment may be so noisy that it may affect the brownout logic, but requiring the system to recover fast enough that the reboot will not be noticed or at least harmful.

    2) Self-healing in case of memory corruption. With constant data protected in flash, and important variables being validated and/or regenerated, the probability of malfunction can be reduced.

    3) Variables initialized by the application are easier to group together into logical blocks and protected by checksums, or possibly redundantly stored.

Children
  • 3) No assurance that the data was explicitly initialized. Any such universal "INIT.A51" type code could group many data-stores into a block and fill that memory space to the 'initialized value' (such as zero), and your ability to point to a specific set of instructions that initialized THAT data-store to THIS value is diluted
    I should have included:
    Every build is set up so each and every (volatile) variable slot (except SFRs and ports which both are set to specific defaults) is ZERO when main() is entered. This process is dead simple when you are not afraid of assembler (all done in local versions of startup.a51)

    also: as I said "as i remember" Per brings up a thing that was included in the considerartion (the boot was too slow, we got a blink of the sign) and I recall that the number of reasons was much higher that those I can recall.

    Erik

  • Well said Per.

    (Once again, I was too verbose in *my* explanation).

    --Cpt. Vince Foster
    2nd Cannon Place
    Fort Marcy Park, VA

  • Reading through this thread makes me wonder what you guys would be like if you all were put into a childrens' playground!

    What hierarchy would there be? How many cliques would there be? How many ostracized individuals?

    Please don't post your answers. It might cause offence!!??

  • How many cliques would there be?

    Two cliques would exist: The Biguns and The Littluns.
    (en.wikipedia.org/.../Lord_of_the_flies)

    Please don't post your answers. It might cause offence!!??
    Okay.

    --Cpt. Vince Foster
    2nd Cannon Place
    Fort Marcy Park, VA