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.
(Score: 3, Insightful) by jmorris on Wednesday April 25 2018, @01:22AM (3 children)
This story is still at zero comments because it lacked the one keyword that would attract attention.
(Score: 4, Interesting) by jimtheowl on Wednesday April 25 2018, @02:23AM (2 children)
What it doesn't contain in bullshit that can easily corrected (therefore the lack of comments), it makes up in content and ingenuity.
I for one would like to express my appreciation for it being posted. I like to play with micro-controllers, and this has given me an new angle to investigate.
(Score: 4, Insightful) by jmorris on Wednesday April 25 2018, @02:42AM (1 child)
We shouldn't have to be reverse engineering DebugWire. But Atmel decided to be dicks about it and now the brand is merged into a bigger, less hacker friendly blob it probably won't get any better. Look at a datasheet, they fully documented the older protocols in great detail but DebugWire they decided to hold closed and try to milk sheckels from developers with... and lock them to their Windows dev tools.
(Score: 2) by jimtheowl on Wednesday April 25 2018, @03:04AM
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