General > General Technical Chat

Is there a reason to avoid putting programming interface pins close?

<< < (3/3)

S. Petrukhin:

--- Quote from: ataradov on January 14, 2021, 03:47:05 am ---Reset is not totally necessary for programming. If it really gets in a way, you can always just drop it from the connector.

--- End quote ---

You can't do without a hardware reset if you use processor sleep modes or have eaten SWD pins for your needs.  :)

ataradov:
Reset does not help if device goes to sleep immediately anyway. Unless there is some way for the debugger to intercept the boot process, like in Atmel MCUs. But that is not very common.

S. Petrukhin:

--- Quote from: ataradov on January 17, 2021, 10:33:38 pm ---Reset does not help if device goes to sleep immediately anyway. Unless there is some way for the debugger to intercept the boot process, like in Atmel MCUs. But that is not very common.

--- End quote ---

With the help of a hardware reset, the processor is possible wakeup and immediately stop the processor, so as not to give the code the opportunity to go to sleep again. I suffered a lot when I studied sleep modes, believe me, life becomes easier when it is there. :)

Berni:
I bring all the associated pins to the programming header regardless if they are used or not. Its not like having a 3 pin or 6 pin connector is that big of a difference. If space is too tight to have one then the only option is likely test points anyway.

Navigation

[0] Message Index

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod