dsPIC/PIC24 multiprogrammer USB Cable not detected

[medelec35]

This is a bit odd. I can load/create flowchart and sends to chip fine. Hardware works OK with no problems at all.
However, If I select 'Chip', 'Configure' then 'Autodetect PICmicro'
I always get the message 'USB Cable is not connected continue?'
Then is select 'Yes' the pop up shows 'PICmico not found from ID 0x0013, please enter the chip name.'


The other thing I found a bit odd (although matrix may have a good reason)? is the value of xtal fitted on programmer = 12MHz. The PLL within dsPIC30F2011 multiplies osc by value by 4
So using pll then freq osc = 12X4 = 48 MHz. Yet the maximum frequency of chip is 40MHz. Would it have been better to use a 10MHz crystal instead?

Still I can't complain, what a powerful range of 16 bit chips!
Very happy with product.
Thank you.

16bit Functions.jpg (46.22 KiB) Viewed 8309 times

Just some of the maths functions.

[Benj]

Hello,

We are currently in a bit of transition with our config / programming software.

PPP is the tool used by Flowcode to assign configuration values. This also used to program standard PIC 12/16/18 devices.

As of Flowcode for dsPIC / PIC24 PPP is used oly as a config tool and a new tool called mLoader is used for programming / communicating to the hardware.

Regarding the crystal values. dsPIC30F devices can run up to 120MHz or 30MIPS therefore a speed of 48MHz or 12MIPs is well within the tolerances.

For further explanation 12MHz was chosen because it worked well with all 3 types of devices in a fairly straightforward manner.

Finally if the crystal is an issue then it is socketed so it can easily be removed with a flat head screwdriver and replaced with a more appropriate value.

[medelec35]

Thanks for that. No Crystal is not an issue, and comment was not meant as criticism at all (no offence intended), as I'm over the moon with the product. I was just wondering as the default target device goes to 40 MHz. Guess I was just curious.
But now you explained the reason I can understand.

As for not detecting I wrongly thought could have been a bug so that's only reason for mentioning it.
I wrongly thought when clicked Autodetect PICmicro, mloader would have done the detection not ppp.
Sorry

Not having a good day today

[Benj]

Not a problem at all in fact i'm glad you asked as it is a bit confusing the way it works when compared to the normal PIC devices. Hopefully we can get it all a bit more polished for v5 so all versions of Flowcode tie in together a bit more.

[wettum]

Hi All,

I'm using for a while the Multiprogrammer board EB-006-00-6 wit Flowcode V4 for PICmicros and the PPPv3.exe program for programming the chip.
Now I installed the Flowcode 4 for dsPIC & PIC24 which uses the mloader v3 for programming and I get the message
"No device detected. Please conect your device or push the reset button".
I can't figure out why he is not getting any contact with the board. Also the automatic chip detection is not finding the chip
(dsPIC33FJ128GP202).
Anyone any idea?

Arie

[Benj]

Hello Arie,

Please can you confirm you are using the EB064 dsPIC board to reprogram the 16-bit devices and not the EB006? The EB006 will only work with 8-bit PIC micros.

[wettum]

Hi Ben,

A bit late but tanks for the answer. You were right, I was thinking that the EB006 board was able to use dsPIC's, sorry that was stupid.

Meanwhile I got the EB064 board and I'm able to use it. However I found some weird behavior with this board.
When I have the RS323 port connected to a 30F2011 or a 33FJ128 I get "FLASH verify failed" errors. I also noticed that in that case
the program was not loaded while it says that it did.

It's easy to reproduce. When I make a simple program with a 30F2011 chip, say only delay 1ms and nothing more, and compile to chip all is fine.
However, when I have only even one RS232 line connected at Port-BL pin 6 I get this listing here. Jumpers on the EB064 are set according the chip.

So my question is, Is it not allowed to compile to chip with peripheral connected, or do I have a problem with this board?

Thanks,

Arie

============================================
File name: C:\Users\wettum\Documents\Projects\Flowcode dsPIC\Experimental\dsPIC30tst\test.c
Generated by: Flowcode v4.4.13.69
Date: Thursday, January 19, 2012 08:54:55
Licence: Professional
Registered to: Arie van Wettum
http://www.matrixmultimedia.com
Launching the compiler...

C:\Program Files (x86)\Matrix Multimedia\Flowcode PIC24&dsPIC V4\Tools\MX_bats\pic16_C30_comp.bat "test" "C:\Users\wettum\DOCUME~1\Projects\FLOWCO~1\EXPERI~1\DSPIC3~1" 30F2011

C:\Users\wettum\Documents\Projects\Flowcode dsPIC\Experimental\dsPIC30tst>pic30-gcc -c -mcpu=30F2011 -funsigned-char -fno-short-double -Os -I"C:\PROGRA~2\MATRIX~1\FLOWCO~1\Tools\MX_bats\..\C_tools\support\h" -I"C:\PROGRA~2\MATRIX~1\FLOWCO~1\Tools\MX_bats\..\MX_support" -Wall -std=gnu99 "test".c -o "test".o
Compilation successful!

Return code = 0
Launching the linker/assembler...
C:\Program Files (x86)\Matrix Multimedia\Flowcode PIC24&dsPIC V4\Tools\MX_bats\pic16_C30_link.bat "test" 30F2011 dsPIC30F
C:\Users\wettum\Documents\Projects\Flowcode dsPIC\Experimental\dsPIC30tst>pic30-gcc -Wl,"test".o,-L"C:\PROGRA~2\MATRIX~1\FLOWCO~1\Tools\MX_bats\..\C_tools\lib",--heap=256,--report-mem,--script="C:\PROGRA~2\MATRIX~1\FLOWCO~1\Tools\MX_bats\..\C_tools\Support\dsPIC30F\gld\p30F2011.gld",-o"test".cof
Program Memory [Origin = 0x100, Length = 0x1f00]

section address length (PC units) length (bytes) (dec)
------- ------- ----------------- --------------------
.text 0x100 0x5aa 0x87f (2175)
.const 0x6aa 0x4 0x6 (6)
.text 0x6ae 0x636 0x951 (2385)
.dinit 0xce4 0x2 0x3 (3)
.isr 0xce6 0x2 0x3 (3)

Total program memory used (bytes): 0x11dc (4572) 38%
Data Memory [Origin = 0x800, Length = 0x400]
section address alignment gaps total length (dec)
------- ------- -------------- -------------------
.heap 0x800 0 0x100 (256)

Total data memory used (bytes): 0x100 (256) 25%
Dynamic Memory Usage
region address maximum length (dec)
------ ------- ---------------------
heap 0x800 0x100 (256)
stack 0x900 0x300 (768)

Maximum dynamic memory (bytes): 0x400 (1024)

C:\Users\wettum\Documents\Projects\Flowcode dsPIC\Experimental\dsPIC30tst>pic30-bin2hex "test".cof
C:\Users\wettum\Documents\Projects\Flowcode dsPIC\Experimental\dsPIC30tst>pic30-objdump -S "test".cof 1>"test".asm
HEX file creation successful!
Return code = 0

Launching the programmer...
C:\Program Files (x86)\Matrix Multimedia\Flowcode PIC24&dsPIC V4\tools\mLoader\mLoaderv3.exe -config -chip 30F2011 "test.hex"
Sending File, please wait!
...................

File sent with 26 warnings:
1: FLASH verify failed [000100]-[000200]
2: FLASH verify failed [000200]-[000300]
3: FLASH verify failed [000300]-[000400]
4: FLASH verify failed [000400]-[000500]
5: FLASH verify failed [000500]-[000600]
6: FLASH verify failed [000600]-[000700]
7: FLASH verify failed [000700]-[000800]
8: FLASH verify failed [000800]-[000900]
9: FLASH verify failed [000900]-[000a00]
10: FLASH verify failed [000a00]-[000b00]
11: FLASH verify failed [000b00]-[000c00]
12: FLASH verify failed [000c00]-[000d00]
13: FLASH verify failed [000d00]-[000e00]
14: FLASH verify failed [000e00]-[000f00]
15: FLASH verify failed [000f00]-[001000]
16: FLASH verify failed [001000]-[001100]
17: FLASH verify failed [001100]-[001200]
18: FLASH verify failed [001200]-[001300]
19: FLASH verify failed [001300]-[001400]
20: FLASH verify failed [001400]-[001500]
21: FLASH verify failed [001500]-[001600]
22: FLASH verify failed [001600]-[001700]
23: FLASH verify failed [001700]-[001800]
24: FLASH verify failed [001800]-[001900]
25: FLASH verify failed [001900]-[001a00]
26: FLASH verify failed [001a00]-[001b00]


Return code = 0

FINISHED

[Benj]

Hello Arie,

We designed E-blocks with current limiting resistors on all I/O lines so this shouldn't be an issue.

Are you using our RS232 E-block or are you using your own hardware connected to the pins?

If it's your own hardware then you could maybe try adding serial resistors to the programming pin data lines. i.e. RB6 and 7.

If it is the E-block causing issues then let me know.

[wettum]

Hi Ben,

Yes it's with the E-block board EB015-00-02.

For the 30F2011 I move the J4 jumper to J6 and make the patch at P2/P1.
When I disconnect the board and compile to chip all is fine. After connecting I can use the RS232 so the board settings are fine.
With the board is connected and I compile to chip again, I get these "FLASH verify failed" warnings and the program is not loaded.

Arie

[Benj]

Hello Arie,

Ok I will make a note of this and see if we can get it resolved in future revisions. Thanks for keeping me updated about the issue.

What position is the flow control jumper on the EB015 board? If you are using jumper setting 1 then maybe try changing this to 2 or 3 and see if this helps.