http://embeddedgurus.com/stack-overflow/2009/05/checking-the-fuse-bits-in-an-atmel-avr-at-run-time/ Thoughts on embedded systems by Nigel Jones Mon, 06 Sep 2010 14:57:18 +0000 http://wordpress.org/?v=2.9.1 hourly 1 http://embeddedgurus.com/stack-overflow/2009/05/checking-the-fuse-bits-in-an-atmel-avr-at-run-time/comment-page-1/#comment-225 Alan Bowens Fri, 22 May 2009 07:12:22 +0000 http://www.gfcdev.org/test-stack/2009/05/15/checking-the-fuse-bits-in-an-atmel-avr-at-run-time/#comment-225 A slight variation on your code sample is to reset the chip if the lock/fuse bits aren't as expected during initialisation. If the chip runs at all, you then know that the bytes are right. A slight variation on your code sample is to reset the chip if the lock/fuse bits aren’t as expected during initialisation. If the chip runs at all, you then know that the bytes are right.

]]> http://embeddedgurus.com/stack-overflow/2009/05/checking-the-fuse-bits-in-an-atmel-avr-at-run-time/comment-page-1/#comment-224 Nigel Jones Wed, 20 May 2009 10:56:34 +0000 http://www.gfcdev.org/test-stack/2009/05/15/checking-the-fuse-bits-in-an-atmel-avr-at-run-time/#comment-224 Greg: I took a look at the link you mentioned. I've never worked with the the PIC24 or dsPIC30 devices and so it wasn't clear to me what's going on. The application note block diagram seemed to indicate that the configuration bits could be read / written on these devices. However there was no mention of it in the text. I then looked at the supplied code. I have to say that the PIC application note code is almost as badly written as some of the atmel application notes. That is functions with no headers, parameters with no explanation, incorrect use of data types, failure to use const etc. As a result I wasn't too much the wiser having looked at the code. When are the microcontroller companies going to start setting an example for the rest of the industry to follow? Greg: I took a look at the link you mentioned. I’ve never worked with the the PIC24 or dsPIC30 devices and so it wasn’t clear to me what’s going on. The application note block diagram seemed to indicate that the configuration bits could be read / written on these devices. However there was no mention of it in the text. I then looked at the supplied code. I have to say that the PIC application note code is almost as badly written as some of the atmel application notes. That is functions with no headers, parameters with no explanation, incorrect use of data types, failure to use const etc. As a result I wasn’t too much the wiser having looked at the code. When are the microcontroller companies going to start setting an example for the rest of the industry to follow?

]]> http://embeddedgurus.com/stack-overflow/2009/05/checking-the-fuse-bits-in-an-atmel-avr-at-run-time/comment-page-1/#comment-223 GregK Wed, 20 May 2009 08:27:17 +0000 http://www.gfcdev.org/test-stack/2009/05/15/checking-the-fuse-bits-in-an-atmel-avr-at-run-time/#comment-223 Microchip deliver simply assembler code what is called from C code to read and write fuse bits. See bootloader aplication from Microchip:http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1824&appnote=en530200 Microchip deliver simply assembler code what is called from C code to read and write fuse bits. See bootloader aplication from Microchip:http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1824&appnote=en530200

]]>