chipKIT® Development Platform

Inspired by Arduino™

50Mhz processor upgrade

Created Fri, 24 Oct 2014 16:21:42 +0000 by nroff-man

nroff-man

Fri, 24 Oct 2014 16:21:42 +0000

Hi

This topic may sound like it's been in a timewarp and comes from the 1990s but using my PIC32 programming software mentioned in my previous post I have upgraded the chipKITPi

The base system comes with a PIC32MX250F128B and the upgrade is a PIC32MX270F256B-50I/SP

This upgrades the chipKITPi from 40MHz, 128KB flash and 32KB RAM to 50MHz, 256KB flash and 64KB RAM. Quite a useful improvement all round.

To perform the upgrade you simply install the chipKITPi bootloader but, to utilise the new features of the chip an object linker script will need to added to your IDE.

Adding the linker script is left as an exercise for those bold enough to upgrade the CPU.

Bye

Quick overview.

After installing the k8048 pic programmer and correctly setting it up you can query the PIC32MX250

% k32 id [1D000000] [PROGRAM] 00008000 WORDS [1F80F220] [DEVICEID] 14D00053 PIC32MX250F128B [1FC00000] [BOOT] 00000300 WORDS [1FC00BF0] [DEVCFG3] CFFFFFFF [1FC00BF4] [DEVCFG2] FFF9FFD9 [1FC00BF8] [DEVCFG1] FF6ACEDB [1FC00BFC] [DEVCFG0] 7FFFFFFB [PE] RIPE_11_000301.hex

After replacing the chip a new query should reveal:

% k32 id [1D000000] [PROGRAM] 00010000 WORDS [1F80F220] [DEVICEID] 26600053 PIC32MX270F256B [1FC00000] [BOOT] 00000300 WORDS [1FC00BF0] [DEVCFG3] FFFFFFFF [1FC00BF4] [DEVCFG2] FFFFFFFF [1FC00BF8] [DEVCFG1] FFFFFFFF [1FC00BFC] [DEVCFG0] 7FFFFFFF [PE] RIPE_11_000301.hex

You can then install the firmware with:

% k32 program chipKIT_Pi.hex

Good luck, bye-bye

EDIT: PS: only replace the chip with the R-Pi power removed.

nroff-man

Sat, 25 Oct 2014 12:49:32 +0000

Lo

Today i have taken the bootloader sources and with the mpide compiler built an MX270 specific chipKIT firmware.

The project can be found here:

[url]http://dev.kewl.org/k8048/Src/asm/chipKITPi/firmware/[/url]

The main edit for the MX270 was a pseudo EEPROM address. I don't know anything about the MPIDE or any other ARDUINO IDE because I never use them but this may fix any problem with that.

Also, it's noticeable, that to get full speed out of this CPU then it would need to be reconfigured.

Bye-bye

Jacob Christ

Sat, 25 Oct 2014 14:50:43 +0000

nroff,

Do you use git? If so you should do some pull requests to get these changes into the repo so they are in a central location.

https://github.com/chipKIT32/PIC32-avrdude-bootloader

If you need help let the thread know...

Jacob

nroff-man

Sat, 25 Oct 2014 15:17:40 +0000

Hi there.

This chipKITPi only project uses the free MPIDE GCC compiler and GNU make and it's not compatible with the build using the commercial MPLAB-X GCC compiler in the GIT repo.

The directory I published above is a clone of my own development repo I have in MERCURIAL (which is superior to git etc :-)

If anyone finds any of this useful then they are urged to use it and copy it as I may or may not update it or even delete it.

Bye-bye

EmbeddedMan

Wed, 29 Oct 2014 23:36:45 +0000

The bootloader project that Jacob mentioned (which has code for all bootloaders for all chipKIT boards) does not use the MPIDE C compiler. It uses XC32 from Microchip, under MPLAB X. Your changes should work just fine. Issue a pull request for the changes you made, and I'll merge them in to the repo.

Thanks for your work in this area!

*Brian

nroff-man

Thu, 30 Oct 2014 00:10:52 +0000

hi :-)

The bootloader project that Jacob mentioned (which has code for all bootloaders for all chipKIT boards) does not use the MPIDE C compiler. It uses XC32 from Microchip, under MPLAB X. Your changes should work just fine. Issue a pull request for the changes you made, and I'll merge them in to the repo.

Please re-read what I wrote, this chipKITPi only bootloader project uses the MPIDE compiler and definitely not the MPLAB-X xc32 compiler which I have no intention of paying for.

I re-factored the Makefiles in this project should anyone wish to expand upon it and those makefiles are definitely not compatible with what's in GIT and they may need some optimisation.

Thanks for your work in this area! *Brian

No problem. Thanks for all the work supporting this bootloader.

I have decided to keep it online for the foreseeable future, in fact, I have created a new tool to upload to it which I am testing now.

Bye-bye

EDIT:typos

EmbeddedMan

Sun, 02 Nov 2014 13:28:22 +0000

nroff-man - Sorry, I missed that. It's really cool that you've written a bootloader using the MPIDE version of XC32. Nice job! Hopefully it will be useful to people running the chipKIT Pi and get more folks excited about the board.

*Brian

nroff-man

Wed, 07 Jan 2015 00:59:29 +0000

Hi

For the record this project didn't need to change much to enable compilation with the MPIDE PIC32 compiler.

I am posting now though to explain that the URL above will soon be removed but new documentation can be found here:

http://wiki.kewl.org/dokuwiki/boards:chipkitpi

This page refers to the new location of the project.

Bye-bye

madias

Sun, 01 Feb 2015 23:09:35 +0000

Just as a side note: The PIC32MX250F128B (without-50) runs for several weeks @48MHZ on my test board. I've read that this MCU goes up to @60+ without problems (not tested). I've included my *.hex file for the supa-dupa-overclocked@48MHZ-PIC32MX250F128B

majenko

Sun, 01 Feb 2015 23:25:39 +0000

From my understanding the -50 is a non -50 that passes the tests at a higher temperature range. The datasheet makes no distinction between the 40MHz and 50MHz versions any more - they just have "the chip" running at 40MHz or 50MHz, and 40MHz allows a greater temperature range than 50MHz.

I run pic32mx250f128b-I/ML chips at 48MHz all the time with no issues at all. In fact, the -50I/ML chips are getting hard to get hold of. MCHP Direct only has a handful of them, and they're not available as samples at the moment.

madias

Sun, 01 Feb 2015 23:34:44 +0000

I run pic32mx250f128b-I/ML chips at 48MHz all the time with no issues at all.

Let me guess: For audio/DAC reasons? ;)

majenko

Sun, 01 Feb 2015 23:48:19 +0000

No, for USB reasons :P

nroff-man

Mon, 02 Feb 2015 09:31:02 +0000

Hi

Just as a side note: The PIC32MX250F128B (without-50) runs for several weeks @48MHZ on my test board. I've read that this MCU goes up to @60+ without problems (not tested). I've included my *.hex file for the supa-dupa-overclocked@48MHZ-PIC32MX250F128B

hi, did you use the MPIDE compiler to create this? I don't think you did, but if so then please provide some detail of how you done it.

btw, I don't actually know what a DP32 is.

Thx,

madias

Mon, 02 Feb 2015 09:54:57 +0000

I've done it with mplab not mpide, just modified the BoardConfig.h, I used the Chipkit DP32 (for sure, it would be smarter to add a new board) #elif defined(BOARD_CHIPKIT_DP32) // 48MHZ mod!! fpllmul + cpu freq!!!

#if defined(PUT_CONFIG_BITS_HERE)

//* Oscillator Settings
#pragma config FNOSC    = PRIPLL                                // Oscillator selection
#pragma config POSCMOD  = XT                                    // Primary oscillator mode
#pragma config FPLLIDIV = DIV_2                                 // PLL input divider
#pragma config FPLLMUL  = MUL_24                                // PLL multiplier
#pragma config FPLLODIV = DIV_2                                 // 20!! PLL output divider
#pragma config FPBDIV   = DIV_1                                 // Peripheral bus clock divider
#pragma config FSOSCEN  = OFF                                    // Secondary oscillator enable

Another step is to add a new board for MPIDE or, better UECIDE and enter the new CPU_F(requency)

DP32: I use this bootloader for my self build PIC32MX250F128B board. The original preprogrammed PIC32MX250F128B (the one with bootloader) has some problems, so I always update a fresh MCU with the "DP32" bootloader.

nroff-man

Thu, 05 Feb 2015 09:48:26 +0000

Hi

I fail to see how it's possible to justify spending > 650 UK pounds to compile a boot loader for a breadboard project.

Consequently, I looked at the USB bootloader for the DP32 and have added it to my project files.

The boot loader compiles OK but I am not able to test it right now.

The instructions are the same as before, found at: http://wiki.kewl.org/dokuwiki/boards:chipkitpi

The hex file is named, CHIPKIT_DP32_48.hex

Please test it if you can, I will see about testing on the ChipKIT Pi at a later time.

Bye

nroff-man

Thu, 26 Feb 2015 16:23:24 +0000

Good day.

I got around to updating the boot loader firmware to now build the USB boot loader for the PIC32 at 48 MHz on the chipKIT Pi.

A boot loader was already available for the MX250 but this extends the range to the MX270 and MX250 at 48 MHz.

The USB boot loader allows the chipKITPi to either run standalone or you can also power the RPi via the GPIO header whilst connected to a powered hub on a separate computer.

The boot loader now has it's own page here: http://wiki.kewl.org/dokuwiki/projects:chipkit32

The original chipKIT Pi page with the pinouts is still here: http://wiki.kewl.org/dokuwiki/boards:chipkitpi

I will add the SDXL target later when I get around to it.

I have also created a 6502 simulator (downgrade?) which works on the chipKIT Pi. This is mostly for fun but can be interesting otherwise. I will post a new thread once it is documented correctly. The page will be an update of this: http://wiki.kewl.org/dokuwiki/projects:ape65

Bye-Bye

nroff-man

Mon, 09 Mar 2015 10:38:34 +0000

Reply to self:

Good day. I will add the SDXL target later when I get around to it.

This target has been added and is working ok.

Bye-bye

GastonLagaffe

Sun, 15 Mar 2015 14:11:12 +0000

Salut,

I have a humble question: I would like to replace the PIC32MX250 on my DP32 with a PIC32MX270. I scanned through the threads here and what google presented me but I could not find a bootloader for the PIC32MX270. I only found the sources but I am not used to build my own bootloader. Before diving into building the bootloader I want to check first if there is a bootloader hex file that I can load onto the PIC32MX270 using PicKit3?

Thanks in advance for any help (and apologies if this sound stupid)

Ciao, Mathias

majenko

Sun, 15 Mar 2015 14:22:24 +0000

The MX270 isn't currently supported by the chipKIT core. It needs adding to the cpudefs.h file, as well as implementing any special settings for it in the rest of the core.

While it would be simple enough to compile a bootloader for it (the MX250 bootloaders should just work fine regardless) you won't really be able to use it with chipKIT yet.

nroff-man

Mon, 16 Mar 2015 08:26:44 +0000

LO

Salut, I have a humble question: I would like to replace the PIC32MX250 on my DP32 with a PIC32MX270. I scanned through the threads here and what google presented me but I could not find a bootloader for the PIC32MX270. I only found the sources but I am not used to build my own bootloader. Before diving into building the bootloader I want to check first if there is a bootloader hex file that I can load onto the PIC32MX270 using PicKit3? Thanks in advance for any help (and apologies if this sound stupid) Ciao, Mathias

There is currently no boot loader hex file for the MX270 at 40 or 48 Mhz for the DP32 or equivalent. Creating one is simple enough and I will do it in a moment and you can test it.

As previously stated by Majenko, there is no linker script for the MX270 as a chipKIT application. Creating one is simple though and an example exists in LED demo directory of this firmware although I have not tested it (in MPIDE) nor do I know how you install it, you can find out and tell us if it is possible.

Bye-bye

I will create a new post when I have created a hex file for testing purposes.

nroff-man

Mon, 16 Mar 2015 08:37:30 +0000

lo

test hex: [url]http://dev.kewl.org/misc/hex/CHIPKIT_DP32_MX270_48.hex[/url]

test linker script: [url]http://dev.kewl.org/misc/hex/chipKIT-application-32MX270F256.ld[/url]

bye

EDIT:

PS. There looks like there are some bugs with this USB boot loader memory mapping. I will see about solving this now.

GastonLagaffe

Mon, 16 Mar 2015 08:48:52 +0000

Salut,

thanks for the hex (really impressive turnaround speed) - I checked the chip I received last week and noticed that I have them in SOIC not in SPDIP. But the SOIC PCB is still in production with OSH. I expect to receive the SPDIP chips by the end of this week and will test then.

Sorry for the delay (I was on a business trip in Saudi Arabia for a week and have to catch up with what happened at home while away)

Ciao, Mathias

nroff-man

Mon, 16 Mar 2015 09:02:54 +0000

Good day

Salut, thanks for the hex (really impressive turnaround speed) - I checked the chip I received last week and noticed that I have them in SOIC not in SPDIP. But the SOIC PCB is still in production with OSH. I expect to receive the SPDIP chips by the end of this week and will test then. Sorry for the delay (I was on a business trip in Saudi Arabia for a week and have to catch up with what happened at home while away) Ciao, Mathias

The delay is no problem.

I already updated the hex file and linker script fixing the `deliberate mistake' in the memory map.

This is all untested but testing it is the only way to fix it. I am glad you prompted this otherwise I wouldn't have even looked closer at it.

Bye-bye

GastonLagaffe

Sun, 22 Mar 2015 23:49:10 +0000

Salut,

I received the chips yesterday and have one now on my HelvePic32 board. I was able to access the chip via PicKit3 and to write the bootloader. The chip acts as expected and I was able to load a sketch to it using UECIDE. I placed the load script in the github directory where I found the other loader scripts but I have no idea how to select this chip in UECIDE. I guess there is some more work to do ...

However, the first step, to get the hardware up and the bootloader running is quite an achievement

Ciao, Mathias

majenko

Mon, 23 Mar 2015 08:59:12 +0000

The chip is selected in the board.txt file. The most important lines to consider when changing your chip to a different one are:

The linker script:

ldscript=chipKIT-application-32MX250F128${upload.${prefs:board.${prefs:board}.programmer}.ldsuffix}.ld

The actual chip in use:

build.mcu=32MX250F128B

The speed the chip runs at:

build.f_cpu=40000000L

You also need to edit cpudefs.h to add the MX270 chip. Duplicate the MX250's entries and bend them to the 270:

#elif defined(__32MX250F128B__)
        #define _CPU_NAME_      "32MX250F128B"
        #define FLASHEND        (((128 - 4) * 1024L) - 1)
        #define RAMEND          ((32 * 1024L) - 1)
        #define __PIC32_PINS__  28
        #define __PIC32MX2XX__

    #elif defined(__32MX250F128C__)
        #define _CPU_NAME_      "32MX250F128C"
        #define FLASHEND        (((128 - 4) * 1024L) - 1)
        #define RAMEND          ((32 * 1024L) - 1)
        #define __PIC32_PINS__  36
        #define __PIC32MX2XX__

    #elif defined(__32MX250F128D__)
        #define _CPU_NAME_      "32MX250F128D"
        #define FLASHEND        (((128 - 4) * 1024L) - 1)
        #define RAMEND          ((32 * 1024L) - 1)
        #define __PIC32_PINS__  44
        #define __PIC32MX2XX__

GastonLagaffe

Mon, 23 Mar 2015 10:44:25 +0000

Salut,

it looks like I am almost there... I changed board.txt:

ldscript=chipKIT-application-32MX270F256${upload.${prefs:board.${prefs:board}.programmer}.ldsuffix}.ld
upload.maximum_size=245760
build.mcu=32MX270F256B
build.f_cpu=40000000L

cpudefs.h:

#elif defined(__32MX270F256B__)
		#define _CPU_NAME_	"32MX270F256B"
		#define	FLASHEND	(((256 - 4) * 1024L) - 1)
		#define	RAMEND		((64 * 1024L) - 1)
		#define	__PIC32MX2XX__

	#elif defined(__32MX270F256C__)
		#define _CPU_NAME_	"32MX270F256C"
		#define	FLASHEND	(((256 - 4) * 1024L) - 1)
		#define	RAMEND		((64 * 1024L) - 1)
		#define	__PIC32MX2XX__

	#elif defined(__32MX270F256D__)
		#define _CPU_NAME_	"32MX270F256D"
		#define	FLASHEND	(((256 - 4) * 1024L) - 1)
		#define	RAMEND		((64 * 1024L) - 1)
		#define	__PIC32MX2XX__

p32xxxx.h:

#elif defined(__32MX270F256B__)
#include <proc/p32mx270f256b.h>
#elif defined(__32MX270F256C__)
#include <proc/p32mx270f256c.h>
#elif defined(__32MX270F256D__)
#include <proc/p32mx270f256d.h>

Copied three files proc/p32mx250f128?.h to proc/p32mx270f256?.h and changed the $ifdef inside to reflect the name Created three directories from the MX250 versions at

c:\UECIDE\compilers\pic32-tools\pic32mx\lib\proc\32MX270F256B\
c:\UECIDE\compilers\pic32-tools\pic32mx\lib\proc\32MX270F256C\
c:\UECIDE\compilers\pic32-tools\pic32mx\lib\proc\32MX270F256D\

It now compiles ok but the load has a problem:

Linking sketch...
C:\UECIDE\compilers\pic32-tools/bin/pic32-gcc -O2 -Wl,--gc-sections -T Not found -T C:\UECIDE\cores\chipKIT/api/chipKIT-application-COMMON.ld -D_USE_USB_FOR_SERIAL_ -w -mprocessor=32MX270F256B -o C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e/Blink.elf C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e\Blink.cpp.o -LC:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e -LC:\UECIDE\cache\chipKIT\HelvePic32 -Wl,--start-group -lCore_api -Wl,--end-group -lm 
C:/UECIDE/compilers/pic32-tools/bin/../lib/gcc/pic32mx/4.5.1/../../../../pic32mx/bin/ld.exe: cannot open linker script file Not found: No such file or directory
collect2: ld returned 1 exit status
Failed linking sketch

Obviously the linked gets called but a file is not found "-T Not found" - but I have no clue what file is missing.

Ciao, Mathias

majenko

Mon, 23 Mar 2015 11:08:30 +0000

It looks to me like you're on the older version of the compiler. You shouldn't have needed to modify anything in the compiler's files if you were using the latest version.

For the "release" version of UECIDE you should be working with the chipKIT-Git core and the pic32-tools-MZ compiler. For the beta version it's sufficient to just use the "chipkit" core, since it's the latest one.

The older compiler lacks the knowledge of how to deal with the newer chips. You need to use the later version.

GastonLagaffe

Mon, 23 Mar 2015 11:43:19 +0000

Salut,

this platform is getting better every day...

I switched to the GIT version and it compiles, loader script is found and ok. I had to duplicate the MX250F128B definitions in the avrdude.conf file and modify the name

#------------------------------------------------------------
# Pic CPU PIC32MX270F256B added by Mathias Wilhelm, March 2015
#------------------------------------------------------------

part
    id               = "pic32-270-256-B";
    desc             = "32MX270F256B";

I then used the blink sketch for testing:

Compiling...
• Compiling sketch...
C:\UECIDE\compilers\pic32-tools-MZ/bin/pic32-g++ -c C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e\Blink.cpp -o C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e\Blink.cpp.o -mprocessor=32MX270F256B -G1024 -g -O2 -fno-exceptions -ffunction-sections -fdata-sections -mno-smart-io -mdebugger -Wcast-align -fno-short-double -DF_CPU=40000000L -DARDUINO=157 -D_BOARD_HELVEPIC32_ -DMPIDEVER=10001932 -DMPIDE=157 -IC:\UECIDE\cores\chipKIT-Git\api -IC:\UECIDE\boards\Boxtec\HelvePic32b -IC:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e -IC:\UECIDE\cores\chipKIT\examples\1.Basics\Blink -D_USE_USB_FOR_SERIAL_ -w 
• Compiling core...
‣ api
• Compiling libraries...
• Linking sketch...
C:\UECIDE\compilers\pic32-tools-MZ/bin/pic32-g++ -Os -Wl,--gc-sections,-Map,Blink.map -mdebugger -mno-peripheral-libs -nostartfiles -T C:\UECIDE\cores\chipKIT-Git\api\chipKIT-application-32MX270F256.ld -T C:\UECIDE\cores\chipKIT-Git\api\chipKIT-application-COMMON.ld -D_USE_USB_FOR_SERIAL_ -w -mprocessor=32MX270F256B -o C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e/Blink.elf C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e\Blink.cpp.o -LC:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e -LC:\UECIDE\cache\chipKIT-Git\HelvePic32 -Wl,--start-group -lCore_api -Wl,--end-group -lm 
C:\UECIDE\compilers\pic32-tools-MZ/bin/pic32-objcopy -O ihex -j .eeprom --set-section-flags=.eeprom=alloc,load --no-change-warnings --change-section-lma .eeprom=0 C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e/Blink.elf C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e/Blink.eep 
C:\UECIDE\compilers\pic32-tools-MZ/bin/pic32-bin2hex -a C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e/Blink.elf 
Compiling done.
Memory usage
C:\UECIDE\compilers\pic32-tools-MZ/bin/pic32-size C:\Users\mawilhel\AppData\Local\Temp\build-b6a73b69-5ef4-4011-b0f6-928b054ffa1e/Blink.elf 
• Program size: 0 bytes
• Memory size: 0 bytes
• Compilation took 0.698 seconds
Uploading firmware...
• Resetting board...
• Uploading...
C:\UECIDE\cores\chipKIT-Git/tools/windows/avrdude -V -p32MX270F256B -P\\.\COM47 -b115200 -CC:\UECIDE\cores\chipKIT-Git/tools/windows/avrdude.conf -cstk500v2 -Uflash:w:Blink.hex:i -v 

avrdude: Version 5.10, compiled on Jan 19 2010 at 10:45:23
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2009 Joerg Wunsch

         System wide configuration file is "C:\UECIDE\cores\chipKIT-Git/tools/windows/avrdude.conf"

         Using Port                    : \\.\COM47
         Using Programmer              : stk500v2
         Overriding Baud Rate          : 115200
         AVR Part                      : 32MX270F256B
         Chip Erase delay              : 9000 us
         PAGEL                         : PD7
         BS2                           : PA0
         RESET disposition             : dedicated
         RETRY pulse                   : SCK
         serial program mode           : yes
         parallel program mode         : yes
         Timeout                       : 200
         StabDelay                     : 100
         CmdexeDelay                   : 25
         SyncLoops                     : 32
         ByteDelay                     : 0
         PollIndex                     : 3
         PollValue                     : 0x53
         Memory Detail                 :

                                  Block Poll               Page                       Polled
           Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
           ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
           eeprom        65    10     8    0 no       4096    8      0  9000  9000 0x00 0x00
           flash         65    10   128    0 yes    131072  256    512  4500  4500 0xff 0xff
           lock           0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
           lfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
           hfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
           efuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
           calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
           signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

         Programmer Type : STK500V2
         Description     : Atmel STK500 Version 2.x firmware
         Programmer Model: STK500
         Hardware Version: 0
         Firmware Version Master : 0.00
         Topcard         : Unknown
         Vtarget         : 0.0 V
         SCK period      : 0.1 us
         Varef           : 0.0 V
         Oscillator      : Off

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x504943
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "Blink.hex"
avrdude: writing flash (9780 bytes):

Writing | ################################################## | 100% 1.30s

avrdude: 9780 bytes of flash written

avrdude done.  Thank you.

• Resetting board...
• Upload Complete

The LED is blinking !!! I am only a bit puzzled by the program size and memeory size being reports as 0

I assume it is safe to remove the non-git compiler

Ciao, Mathias

majenko

Mon, 23 Mar 2015 11:44:59 +0000

The size is reported as 0 because the output from the new compiler's "size" command changed from the older version. It's not being parsed right is all.

nroff-man

Mon, 23 Mar 2015 12:19:57 +0000

Hi

Make sure you set the project oscillator to 48 MHz otherwise the timing will be wrong. The boot loader should set the clock to 48000000.

Bye