chipKIT® Development Platform

Inspired by Arduino™

any way to Factory reset an UNO32 that is Not responding?

Created Wed, 17 Apr 2013 11:47:25 +0000 by caroper

caroper

Wed, 17 Apr 2013 11:47:25 +0000

Hi All,

I have been mainly working with PIC32MX1/2 Dip packages on a breadboard lately so have not used my UNO32 board for a couple of years, but I just pulled it out of the cupboard to try something and it appears to be dead :(

This is a new PC since I last used it so I installed the latest MPIDE 0023-windows-20120903 on windows XP PRO, SP3, 32bit.

It is detected, the Power LED is on and no shields are connected, I then loaded the Blink Sketch to test the instillation.

When I try to upload the progress gets to 95%, LED1 blinks periodically, but everything just hangs.

I have the Correct Board Selected and the Correct COM port. I have updated to the latest FTDI drivers etc. but still nothing.

I have no idea what the board was last used for but I am sure it was working.

Is it possible to reset it to factory condition? Do I need a new Bootloader to go with the New MPIDE? Any faultfinding suggestions?

Cheers Chris

majenko

Wed, 17 Apr 2013 12:12:51 +0000

You could try re-flashing the bootloader if you have a hardware programmer available (pickit2 or pickit3).

If you have an oscilloscope you can take a look at the clock signal coming from the oscillator to see if it's running.

If you don't have either of those then it's going to be hard to diagnose it.

caroper

Wed, 17 Apr 2013 14:08:26 +0000

Thanks,

I have Pickit 2 and 3 and an ICD 3 so getting a new bootloader on shouldn't be a problem, but which one do I use, git hub has several now.

I don't have a scope but I do have a logic analyzer so will do as suggested and take a look at the clock signal.

I take it there are no known faults I should look for when it has been left standing or re installed?

Time to start pulling out all the hardware development tools. So much for a quick test of an idea, I may just continue with the DIP packages as they are setup on the bench already and shelve the UNO32 for now then.

Cheers Chris

majenko

Wed, 17 Apr 2013 14:11:19 +0000

I usually use the one on the UNO32 product page - works fine on mine. It's a little out of date, but works.

Eventually the IDE will have bootloader burning facilities (my test version already has it).

caroper

Wed, 17 Apr 2013 15:25:40 +0000

Very strange, updating the Bootloader has not helped. here is the log:

PICkit 3 detected Connecting to PICkit 3... Running self test... Self test completed Firmware Suite Version...... 01.28.40 Firmware type......................PIC32MX Downloading AP... AP download complete Running self test... Self test completed Firmware Suite Version...... 01.28.40 Firmware type......................PIC32MX PICkit 3 Connected. Target Detected Device ID Revision = 50900053

Reading... Read Complete (I did a read just to confirm the communications, at this point I saved to old image and imported arduino-bootloader.X.Uno32_8-19-11.hex), Programming... Programming/Verify complete

Target Removed

The chip is running fine and must be programming fine else the varify would have failed. But I still have the same issue of the upload hanging.

How would I test the FTDI section to see if that is working?

Cheers Chris

EDIT:

Problem appears to have been resolved but I have no idea how. I ran FT_Prog to see if I could detect the FTDI Chip, It said device is still enumerating, so I unplugged the USB cable, Plugged it back in and FT_Prog reported the Chip details. BUT Simultaneously the Green LED began to Blink, the sketch is Running.

maybe the FTDI chip needed a reset.

delebel

Thu, 03 Mar 2016 16:23:49 +0000

I'm a newbie but I have similar problems, I use mplab x (with pic3 programmer) to upload the original boot loader provided by Diligent to my Uno32 board yet so far no one sketch (blink included) has been successfully ran on the board. The sketch compiles ok but the upload takes forever (minutes) to finally report several erros which suggest a timeout termination situation. The loader file name: aduino-bootloader.X.Uno32_8-19-11.hex . The blink program tried is shown as an attachement and the error message below. At this stage I'm still torn between straight C programming with Mlap since I can get a blink version working via that route. However I was curious about the Arduino environment to gain access to the libraries that would accelerate my development. The arduino package is shown as Arduino 1.6.7 (from chipkit) and the Any comments welcome...Denis

Arduino: 1.6.7 (Windows 8.1), Board: "Arduino/Genuino Uno"

Sketch uses 1,030 bytes (3%) of program storage space. Maximum is 32,256 bytes. Global variables use 9 bytes (0%) of dynamic memory, leaving 2,039 bytes for local variables. Maximum is 2,048 bytes. avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x2b avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x2b Problem uploading to board. See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.

This report would have more information with "Show verbose output during compilation" enabled in File > Preferences.

majenko

Thu, 03 Mar 2016 21:39:20 +0000

Do you have the chipkit-core installed in the Ardunio IDE? And do you have the Uno32 board selected?

guymc

Thu, 03 Mar 2016 22:05:30 +0000

Do you have the chipkit-core installed in the Ardunio IDE? And do you have the Uno32 board selected?

If you need help with those steps, see the excellent tutorial here:

[url]https://quick240.com/quicki/chipkit:education[/url]

delebel

Thu, 10 Mar 2016 16:11:18 +0000

If you need help with those steps, see the excellent tutorial here: [url]https://quick240.com/quicki/chipkit:education[/url]

In my Arduino the nearest core available is the Arduino/Genuino Uno selection. Am I to understand there is a specifc chipkit core version out there somewhere?

majenko

Thu, 10 Mar 2016 17:09:22 +0000

Well, yes? The Arduino boards are completely different. Like the difference between a push bike and an F1 racing car.

Everything you need to know is on the website under the heading of "Getting Started". http://chipkit.net/started/

delebel

Fri, 11 Mar 2016 18:20:23 +0000

Well I got Led4 on the un32 to flash after reloading the original boot loader from diligent but it is flashing faster then I would expect from the blink sketch that I tried to load so I'm not sure what happening. Does the bootloader flash any leds to indicate it is active because the sketch loading failed but the loader programming with mplabx + the pic3 programmer did indicates a successful program/verify sequence? As for the sketch loading failure I do not actually have a UNO32 in the selection box the nearest is the "Arduin/Genuino Uno". This with the Arduino 1.6.7 loaded. I did initially tried the Mpide Arduino version 23 but after reading some posts I got the impression I would be more appropriate to use the version from the chipkit site (1.6.7). My next move is to track down the avrdude: stk500_recv(): programmer is not responding error message to attempt to identify the source of the problem.

Thanks Denis

majenko

Fri, 11 Mar 2016 18:27:38 +0000

If you had installed the chipkit-core through the boards manager you would have the Uno32 in the list. Until you do that you cannot program your Uno32. Even though both that and the Genuino have the letters U N and O in them they are NOT the same thing.

Get that chipkit-core installed.

delebel

Wed, 23 Mar 2016 14:26:43 +0000

Thanks I finally got the blink to work. I reload the chipkit arduino package again and used the menus to install the UNO32 board. So for any newbie out there the Genuino Uno board IS NOT! compatible with the UNO32. The board selection MUST show the UNO32 selection or it won't work.

Regards Denis Lebel