Created Thu, 06 Dec 2012 21:48:40 +0000 by Brainiac
Thu, 06 Dec 2012 21:48:40 +0000
Hello! I have chipkit programmer and max32 board. I tryed to debug simple project of blinking led in mplab x ide. when i push "run" - led is blinking and all right when i push "debug main project" - the process hovers at this moment:
***************************************************** Connecting to Licensed Debugger... Firmware Suite Version.....01.28.18 Firmware type..............PIC32MX chipKITProgrammer by Digilent Target detected Device ID Revision = 4300053 program memory: boot config memory configuration memory Programming...
and thats all can anybody help me?
Fri, 07 Dec 2012 16:13:00 +0000
I have experienced this also. Can you tell me what rev of the MAX32 you have? Or, what is easier, tell me if the MAX32 has 1 or 2 LEDs on the board.
Sat, 08 Dec 2012 14:10:38 +0000
i have max32 revision C max32 has 4 leds on board - 1 for power, 2 for usb and one for pic32 :)
Mon, 10 Dec 2012 03:20:54 +0000
Very interesting, that breaks my hypothesis; I have no clue exactly what is going on. It seems to happen to only certain Max32s. But it happens, I've got one it happens on, but mine is a Rev D with 2 PIC32 LEDs on it. All of my Rev C Max32 work.
Do me a favor, I can "program" but I can not "debug program". Can you try to "program" something; like try reprograming the bootloader?
Also, just so you know, a PICkit3 seems to work for me.
Hmmm.... let me do some more research... and thanks for proving my hypothesis wrong; I won't continue down that path.
Tue, 11 Dec 2012 00:45:47 +0000
i want try to decide this problem another way... when i programmed mcu, i see:
***************************************************** Connecting to Licensed Debugger... Firmware Suite Version.....01.28.18 Firmware type..............PIC32MX chipKITProgrammer by Digilent Target detected Device ID Revision = 4300053 program memory: boot config memory configuration memory Programming... Programming/Verify complete The target device is not ready for debugging. Please check your configuration bit settings and program the device before proceeding.
configuration settings are
// Configuration Bits #pragma config FNOSC = PRIPLL // Oscillator Selection #pragma config FPLLIDIV = DIV_2 // PLL Input Divider (PIC32 Starter Kit: use divide by 2 only) #pragma config FPLLMUL = MUL_20 // PLL Multiplier #pragma config FPLLODIV = DIV_1 // PLL Output Divider #pragma config FPBDIV = DIV_1 // Peripheral Clock divisor #pragma config FWDTEN = OFF // Watchdog Timer #pragma config WDTPS = PS1 // Watchdog Timer Postscale #pragma config FCKSM = CSDCMD // Clock Switching & Fail Safe Clock Monitor #pragma config OSCIOFNC = OFF // CLKO Enable #pragma config POSCMOD = XT // Primary Oscillator #pragma config IESO = OFF // Internal/External Switch-over #pragma config FSOSCEN = OFF // Secondary Oscillator Enable #pragma config CP = OFF // Code Protect #pragma config BWP = OFF // Boot Flash Write Protect #pragma config PWP = OFF // Program Flash Write Protect #pragma config ICESEL = ICS_PGx2 // ICE/ICD Comm Channel Select #pragma config DEBUG = ON // Debugger Disabled for Starter Kit
are there errors???
Wed, 12 Dec 2012 18:25:54 +0000
We have identified that there was a manufacturing error with the chipKIT PGM. There was a mistake made in following our enginerring change control process and a required component value change didn't get implemented. R12 and R13 are supposed to be 330 ohm resistors but 100 ohm resistors were loaded instead. The result will be erratic operation of the module. They work well enough to pass our manufacturing test, but don't actually work reliably.
We have halted shipments of the current production modules. We will replace, at no charge, any chipKIT PGM sold to date. Contact Digilent customer support to obtain an RMA number and we will send you a new one. We anticipate having corrected modules available for shipment around the first of January.
Anyone who wants to can try replacing R12 and R13 with 0402 size, 330 ohm, 5% resistors themselves. If you do that, we won't void your warranty and will still replace your module when we receive the corrected ones, if you so desire. However, I would not recommend attempting this unless you are moderatly skilled at surface mount rework :).
I apologize for any inconveniece that this has caused.
Gene Apperson Digilent