Re: Urgent help needed for programming IOIO v1 with a Pickit 3

[Ytai Ben-Tsvi]

Why are you using mplab 8?
Mpblab-x works natively on osx.

On Feb 20, 2013 5:03 PM, "Hector" <hce...@gmail.com> wrote:

Hello,

I'm trying to program a IOIO v1 ( PIC24FJ256DA206 chip and board dated 4-6-11 ) using a Pickit 3.

Connections between the two are:

Pickit 1 - mclr

Pickit 2 - 3.3v

Pickit 3 - GND

Pickit 4 - PIN36

Pickit 5 - PIN35

The IOIO is connected to the power using 5v (without powering it, MPLAB doesn't see any device connected).

I installed MPLAB IDE v8.89, went to devices and selected the PIC24FJ256DA206 chip then opened Programmer/Select Programmer/Pickit 3 and after trying to connect for a short time I get:

Target Device ID (00000000) does not match expected Device

ID (410c0000).

I tested all the connections and they seem to be fine. The IOIO is otherwise functional. I'm trying to upgrade the firmware to add Bluetooth support and I don't have another IOIO available. I'm using Windows XP running inside Parallels on Mac OS Mountain Lion. I found testimonials in the Microchip forum about other people successfully using the Pickit 3 in Parallels (I'll try to get hold of a PC for testing).

Any help will be greatly appreciated since this is for a project due in two days.

Thanks!

Hector

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ioio-users+...@googlegroups.com.
To post to this group, send email to ioio-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ioio-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Hector]

Hello Ytai,

Thank you very much for your reply.

Yes, after sending my message I found out about Mplab X. I tried it already and it gave me the same results. I get:

Target Device ID (0x0) does not match expected Device ID (0x410c0000).

Now the ioio is not working when connected to an Android device. The power LED is on but the device doesn't react to it. Is it possible that the board is already damaged?

[Ytai Ben-Tsvi]

It's possible that the PIC is dead or that the connection to the programmer is bad.

[claire delaunay]

Each time I got that problem was because I was using wires too long or not well connected between the pickit3 and the ioio.

2013/2/20 Ytai Ben-Tsvi <yta...@gmail.com>

[Hector]

Thank you Claire! I changed the wires for very short ones and now it gets detected by MplabX saying:

Target detected

Device ID Revision = 3

How long should it take to program it? Something seems to not be quite right because after loading the hex file ( I'm using SPRK0016.hex from Boot-IOIO0310-App-IOIO0330 ) and after pressing Erase and then Program it takes just about two seconds before it displays Programming complete. Is this right? I also ran a Verify, that takes much longer (about a minute or more), and it claims to be OK. Still my Android device doesn't detect it.

...

Ok, I just tested with the Boot-IOIO0306-App-IOIO0326 version and it seems that it's back to life! The programming took longer and now my device is detecting it. Does IOIO0306 also implements Bluetooth support? A quick test with an old dongle didn't work but it might be the dongle not being compatible.

Thanks again!

[Ytai Ben-Tsvi]

3.26 is the recommended one for IOIO V1.

[Shane Wilson]

I can successfully program PIC24FJ256DA206 and I found that this message comes for me when I disconnect the DATA line (pickit pin# 4).

Target Device ID (00000000) does not match expected Device ID (410c0000)

Pickit 1 - mclr

Pickit 2 - 3.3v

Pickit 3 - GND

Pickit 4 - PIN36  (DATA)

Pickit 5 - PIN35  (CLOCK)


I also found that this message disappears when I connected an oscilliscope to pin#4,  but remove the oscilliscope and the error comes back..  wow thats pretty crazy. 

what does this mean?  what does my oscilloscope add to the DATA line that makes it work?   can I build this into my programming circuit by way of small resistor, who would I configure it in the circuit?

[Ytai Ben-Tsvi]

Sounds like a ground-related issue. Try powering the IOIO only from the programmer and I bet the problem will go away.