hi, in my fubarino mini board debugging is not working. but i am able to program the IC. while trying to debug it is showing an error message

"Programming/Verify complete"
"The target device is not ready for debugging. Please check your configuration bit settings and program the device before proceeding. The most common causes for this failure are oscillator and/or PGC/PGD settings."

here 8MHz crystal frequency is multiplied to 40MHz using PLL.
I am using MPlabX IDE. i am using PGED1 and PGEC1 for programming. i have also tried with PGED3 and PGEC3 but the result is same error message.
configuration bit settings that i am using is also given below

// PIC32MX250F128D Configuration Bit Settings

// 'C' source line config statements

include <xc.h>

// DEVCFG3
// USERID = No Setting

pragma config PMDL1WAY = OFF // Peripheral Module Disable Configuration (Allow multiple reconfigurations)

pragma config IOL1WAY = OFF // Peripheral Pin Select Configuration (Allow multiple reconfigurations)

pragma config FUSBIDIO = OFF // USB USID Selection (Controlled by Port Function)

pragma config FVBUSONIO = OFF // USB VBUS ON Selection (Controlled by Port Function)

// DEVCFG2

pragma config FPLLIDIV = DIV_2 // PLL Input Divider (2x Divider)

pragma config FPLLMUL = MUL_20 // PLL Multiplier (20x Multiplier)

pragma config UPLLIDIV = DIV_12 // USB PLL Input Divider (12x Divider)

pragma config UPLLEN = OFF // USB PLL Enable (Disabled and Bypassed)

pragma config FPLLODIV = DIV_1 // System PLL Output Clock Divider (PLL Divide by 1)

// DEVCFG1

pragma config FNOSC = PRIPLL // Oscillator Selection Bits (Primary Osc w/PLL (XT+,HS+,EC+PLL))

pragma config FSOSCEN = OFF // Secondary Oscillator Enable (Disabled)

pragma config IESO = OFF // Internal/External Switch Over (Disabled)

pragma config POSCMOD = HS // Primary Oscillator Configuration (HS osc mode)

pragma config OSCIOFNC = OFF // CLKO Output Signal Active on the OSCO Pin (Disabled)

pragma config FPBDIV = DIV_2 // Peripheral Clock Divisor (Pb_Clk is Sys_Clk/2)

pragma config FCKSM = CSDCMD // Clock Switching and Monitor Selection (Clock Switch Disable, FSCM Disabled)

pragma config WDTPS = PS1048576 // Watchdog Timer Postscaler (1:1048576)

pragma config WINDIS = OFF // Watchdog Timer Window Enable (Watchdog Timer is in Non-Window Mode)

pragma config FWDTEN = OFF // Watchdog Timer Enable (WDT Disabled (SWDTEN Bit Controls))

pragma config FWDTWINSZ = WINSZ_25 // Watchdog Timer Window Size (Window Size is 25%)

// DEVCFG0

pragma config JTAGEN = ON // JTAG Enable (JTAG Port Enabled)

pragma config ICESEL = ICS_PGx1 // ICE/ICD Comm Channel Select (Communicate on PGEC1/PGED1)

pragma config PWP = OFF // Program Flash Write Protect (Disable)

pragma config BWP = OFF // Boot Flash Write Protect bit (Protection Disabled)

pragma config CP = OFF // Code Protect (Protection Disabled)

On v1.6 mini schematic 5v is connected to pin 42 (vbus) on micro. What would happen if Vin was used and greater than max voltage allowed on vbus input at micro (+5.5v). I think this port should be changed to Vbus instead of the 5v port.

I have spent several months using FubarinoSD, communicating with it via USB serial using a freeware PC terminal called "Realterm". No problems there. However, to collect files of data from the SD I now need to use a VB.NET2012 terminal. This VB.NET terminal works fine with an Arduino Due and can send but not receive from the SD. However the SD is faster and I need to use it. This is using essentially identical software in the Due and the SD (I use UECIDE). Please explain how I can overcome this apparent bug in the SD. I have posted example software on the Fubarino SD forum as
"randomrichard" yesterday.

Update Fubarino Mini with update SPI MISO 27

The mini is coming. Add documentation.

Hi! We are trying to take advantage of Fubarino SD RTC.
We changed the bootloader so the BoardConfig.h so we have now:

pragma config FSOSCEN = ON

within

elif defined(BOARD_FUBARINO_SD_512K_USB)

We uploaded the new bootloader with an ICD3 and reuploaded the ChipKit sketch.
This sketch makes an GPRS transaction and get the date/time from the network.
This works.
But the time does not change within the RTC and we do not see the Cristal waves with an oscilloscope.
The class used is RTCC from Majenko.

Any idea would be very very welcome!

Christophe

sorry, didn't find another place to submit this...fubarino SD with dsPIC/DAC would be one of those things ..
ie http://www.microchip.com/wwwproducts/Devices.aspx?dDocName=en532310

Microchip indicates there is no more Fubarino Mini in stock. End of January 2014 is the real restocking planning ????

Your title page and the Microchip website states that it is the L variant but it is actually the H variant. Which is a huge lucky break for me on a project I am working on that needs the H variant.

I'm working on an interrupt lab for the Fubarino Mini 2.0 for my class.

I have found that the macros PIN_INT0-4 are defined as the following in Board_Defs.h:

#define	PIN_INT0	24		// B7   non-PPS
#define	PIN_INT1	3		// B14  INT1R = RPB14 = 1
#define PIN_INT2	0		// B13  INT2R = RPB13 = 3
#define	PIN_INT3	6		// A1   INT3R = RPA1 = 0
#define	PIN_INT4	4		// B15  INT4R = RPB15 = 3

Board_Data.c has the following array defined:

const uint8_t external_int_to_digital_pin_PGM[] = {
	NOT_PPS_PIN,			// INT0 is not mappable
	PIN_INT1,				// INT1
	PIN_INT2,				// INT2
	PIN_INT3,				// INT3
	PIN_INT4				// INT4
};

If I use:

   attachInterrupt(PIN_INTx, isrX, MODE);

Where PIN_INTx is a defined interrupt pin and isrX is function that prints out a value if called that looks something like this:

void isr0() 
{ 
  digitalWrite(LED_BUILTIN, !digitalRead(LED_BUILTIN)); // toggle pin 1
  Serial.println("ISR0");
}

I find that:

PIN_INT1 is mapped to pin 6 RISING or FALING
PIN_INT2 is mapped to pin 24 RISING or FALING
PIN_INT4 is mapped to pin 4 RISING or FALING

None of the CHANGE interrupt modes work (there is no code to support this type in WInterrupts).

Also, PIN_INT0 and PIN_INT3 do not seem to be working, didn't dig too deep to understand why.

Hi, I think I accidentally shorted Vout to GND with power on the board... it no longer boots, the power LED flickers a little.

Is there any way I can still use this board? a soft fuse or something that will heal over time?

Thanks

It looks like two I2C ports are called out on the diagram for the Fubarino SD, but its not clear which are SCL and SDA and which are the defaults for use with Wire.begin().

So a common failure mode of the Fubarino SD and Mini is when students short 3.3V to GND (for too long). This causes the regulator to go and the board to stop working. So I sat down today to try and repair some five blown boards and found that the when powered with USB that Vout will have between 14-25VDC on it. The 3.3V output will also have a large voltage and this has probably fried the processors too. I suspect that the failed regulator, D1 and C3 are working together to form some kind of charge pump. Very strange.

On
http://fubarino.org/sd/index.html
the second bullet should read "MultiPlatform IDE", not "MulitPlatform IDE", both for the 1.5 and 1.4 variants.

This should be fairly simple, but we should have pictures of the Mini as well as the SD, and text explaining both on the main landing page.

In addition, www.fubarino.org/mini should go to a page that goes somewhere useful, like page that talks about the mini.

Hi, the PIC32 is fully JTAG programmable as well, and is even supported with OpenOCD.

Are the JTAG pins exposed on this device? Are there any other limitations that would make JTAG programming impossible?

You have this:
SDO, MISO
SDI, MOSI

When its actually supposed to be:
SDO, MOSI
SDI, MISO

Here: https://github.com/fubarino/fubarino.github.com/wiki/SD-Board-Pin-Features

Hi! Looking at PIN_CNx in Board_Defs.h of FubarinoSD, the Arduino pin numbers do not fit with the User Manual and the MCU data. I would propose:

define PIN_CN0 6

define PIN_CN1 5

define PIN_CN2 34

define PIN_CN3 33

define PIN_CN4 32

define PIN_CN5 31

define PIN_CN6 30

//#define PIN_CN7 RB5

define PIN_CN8 24

define PIN_CN9 25

define PIN_CN10 26

define PIN_CN11 27

define PIN_CN12 44

define PIN_CN13 10

define PIN_CN14 11

define PIN_CN15 12

define PIN_CN16 13

define PIN_CN17 28

define PIN_CN18 29

Am I right or wrong?

I searched for code supporting ChangeNotification and did not really found something "Arduino minded" excepted for Majenko proposal in SourceForge (why is it not integrated in ChipKit?) which works perfectly.

Any suggestion welcome!

My company bought a half dozen or so Fubarino SD's for a rapid prototype for a customer and they worked great. However I was running my own native PIC code, not MPIDE code.

My company has no more need for these prototypes and I want to use them to teach basic programming skills to a group of kids. I want to be able to use them with MPIDE again. Can you please post / provide binaries and instructions? I have access to a Pickit programmer as well as several ICD 3's.
Thanks,
David

SPI SCK is on the wrong pin. The picture in the manual appears to be correct (SCK on pin 3/RB14).

The PNG is also wrong:
fubarino.github.com/mini/docs/FubarinoMini1_5Diagram.png

The SVG does appear to be correct.

Probably just need to regenerate the pdf and png from the svg.

I'm am prototyping a new board with the Fubarino Mini 2.0. Both the Fubarino Mini 2.0 web page and the Microchip Direct web page indicate that the board has a PIC32MX250F128D-50I/ML while the actual physical board in my possession and the linker scripts selected in the boards.txt file are for the PIC32MX270F256.

excerpt from boards.txt:

# Fubarini Mini v2.0

fubarino_mini_20.ccflags=-Map="map.map"
fubarino_mini_20.ldscript=chipKIT-application-32MX270F256.ld

I actually noticed the discrepancy when building the project and seeing that the Maximum program space didn't match the PIC32MX250F128D:

Sketch uses 29916 bytes (12%) of program storage space. Maximum is 245760 bytes.
Global variables use 7752 bytes (12%) of dynamic memory, leaving 55736 bytes for local variables. Maximum is 63488 bytes.
    Copyright: (C) 2011-2015 Serge Vakulenko
                   2016-2017 Majenko Technologies
Programmer for Microchip PIC32 microcontrollers, Version 2.1.46
      Adapter: STK500v2 Bootloader
 Program area: 1d000000-1d1fffff
    Processor: Bootloader
 Flash memory: 2048 kbytes
  Boot memory: 80 kbytes
         Data: 31220 bytes
        Erase: done
Program flash: .................................################################## done
 Verify flash: .................................################################# done
 Program rate: 6371 bytes per second

And a picture of the chip on my board:

After downloading via the USB Serial port, the USB Serial port drops out and the application cannot re-establish the USB Serial connection (e.g. Serial(115200)) does not start and the USB serial link is not started even when "Serial" is selected in the IDE

Hi I am using a Fubarino SD board with arduino and code that has been previously working is now bringing up this error code, anyone have an idea of what it is?
Thanks

It seems like it would be a good idea.

Fubarino Mini ICSP headers documentation needs adding to manual

FubarStep board now exists. It's time to start creating the documentation for it. Add to the wiki the board information.