On Wed, Aug 4, 2010 at 1:01 AM, Michael Schwingen
wrote:
> On 08/03/2010 12:01 PM, zeal wrote:
>>
>> This patch add the below commands (just for determining stuff).
>>
>> 1. read_bits for reading Fuse/Lock bits.
>> 2. read_byte for reading Signature/Calibration byte.
>>
>
> This looks good - ho
simon qian wrote:
> And there is a unique ID in signature row of some AVR.
> May be it's an interesting feature to use.
>
> Is there any safe way to support AVR fuse/lock writing?
> As you know, such code is very simple, both for JTAG and ISP.
> Yes, It's really dangerout to write these sections,
And there is a unique ID in signature row of some AVR.
May be it's an interesting feature to use.
Is there any safe way to support AVR fuse/lock writing?
As you know, such code is very simple, both for JTAG and ISP.
Yes, It's really dangerout to write these sections, especially fuse.
So I didn't t
On 08/03/2010 12:01 PM, zeal wrote:
This patch add the below commands (just for determining stuff).
1. read_bits for reading Fuse/Lock bits.
2. read_byte for reading Signature/Calibration byte.
This looks good - however, I have issues with the command names: both
names do not represen
This patch add the below commands (just for determining stuff).
1. read_bits for reading Fuse/Lock bits.
2. read_byte for reading Signature/Calibration byte.
Usage as below:
1. avrf read_bits
2. avrf read_byte
is the type of byte you want to read.
is the location of that byte.
