Stories
Slash Boxes
Comments

SoylentNews is people

Dissecting The AVR Debugwire

posted by Fnord666 on Tuesday April 24 2018, @04:51PM   Printer-friendly
from the on-the-wire dept.

Arthur T Knackerbracket has found the following story:

Anyone who’s ever written more than a dozen or so lines of code knows that debugging is a part of life in our world. Anyone who’s written code for microcontrollers knows that physical debugging is a part of our life as well. Atmel processors uses a serial communications protocol called debugWire, which is a simpler version of JTAG and allows full read/write access to all registers and allows one to single step, break, etc. [Nerd Ralph], a prominent fixture here at Hackaday has dug into the AVR debugWire protocol and enlightened us with some valuable information.

Original Submission

 
This discussion has been archived. No new comments can be posted.
Dissecting The AVR Debugwire | Log In/Create an Account | Top | 4 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by jimtheowl on Wednesday April 25 2018, @03:04AM

    by jimtheowl (5929) on Wednesday April 25 2018, @03:04AM (#671490)
    I agree, but I'm not going to knock Atmel too much as I think they have had an overall very positive influence for hackers. It is common for the engineers to have to 'negotiate' something with management that they can leave out for the sake of ensuring the future flow of 'sheckels'.

    If they do get significantly less hacker friendly, there are plenty of alternatives. For instance I am just about to attempt to burn Mecrisp FORTH on a cheap F103C8T6 ARM STM32.
    That is the performance version based on the ARM Cortex-M3.
    https://en.wikipedia.org/wiki/STM32#STM32_F1
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2