TheBackShed.com

Forum Index : Microcontroller and PC projects : Pic-kit3 Dead ??

Page 2 of 2

Author

Message

robert.rozee
Guru

Joined: 31/12/2012
Location: New Zealand
Posts: 2430

Posted: 01:26am 18 Sep 2016

Copy link to clipboard

Print this post

3v6 should be fine. the MX170/MX470 is rated for 2.3v to 3.6v when operating, with an absolute maximum of 4.0v. geoff has done tests and had devices survive on 5.0v although this is not to be recommended long-term.

i've used cheap 3v3 zener diodes from china and seen actual voltages from 2.9v up to 3.9v delivered to an MX170 by the programmer, all without any issues.

phil23 said I see there's a read option.
Can I use this to read the pic & create Hex files.

there is indeed a read option. when you work out how to use it, please let us all know! i've never tried reading a device, but in theory it should work. no guarantee of the read speed though, i would expect it to be fairly slow.

cheers,
rob :-)

atmega8

Guru

Joined: 19/11/2013
Location: Germany
Posts: 724

Posted: 08:44am 18 Sep 2016

Copy link to clipboard

Print this post

Thank you ROB,

my Z-Diode gives exactly 3,6 Volt.
Other than you China "Crackers" ;-).

You could not answer Phil 23 Question regarding the read option.
Wasn't it you who developed the code?

THX from Germany

Phil23
Guru

Joined: 27/03/2016
Location: Australia
Posts: 1667

Posted: 10:23am 18 Sep 2016

Copy link to clipboard

Print this post

robert.rozee said there is indeed a read option. when you work out how to use it, please let us all know! i've never tried reading a device, but in theory it should work. no guarantee of the read speed though, i would expect it to be fairly slow.

[Code]Read memory:
pic32prog -r file.bin address length

Args:
file.srec Code file in SREC format
file.hex Code file in Intel HEX format
file.bin Code file in binary format
-v Verify only
-r Read mode
-d device Use specified serial or USB device
-b baudrate Serial speed, default 115200
-B alt_baud Request an alternative baud rate
-e Erase chip
-p Leave board powered on
-D Debug mode
-h, --help Print this help message
-V, --version Print version
-C, --copying Print copying information
-W, --warranty Print warranty information
-S, --skip-verify Skip the write verification step[/code]

I think the two parameters, address & length are questions for Geoff or matherp.

I'd suspect it's different between devices.

Also the help reports file.bin, may or may not be relevant.

Phil

robert.rozee
Guru

Joined: 31/12/2012
Location: New Zealand
Posts: 2430

Posted: 01:53pm 18 Sep 2016

Copy link to clipboard

Print this post

atmega8 said You could not answer Phil 23 Question regarding the read option.
Wasn't it you who developed the code?

only parts of it.

pic32prog is a project developed and maintained by Serge Vakulenko. the project was started in 2011, not long after Serge began working for MIPS (the company that developed the M4K core used in pic32 processors).

Serge supplied to me a 'skeleton' module to develop the 'ascii ICSP' support with. i designed a communications protocol to talk between an arduino NANO and pic32prog, and wrote code within the supplied 'skeleton' to use this protocol for communications with a custom programmer. i also developed the code that runs on the arduino (atmega328p based) programmer - others have adapted this code for different hardware (such as jean's commercial version, and peter's open-source PIC16F1455 version). the development was spread out over 15 months or so.

all the code i wrote operates at a very low level, whereas the high level functionality like 'read out all of flash', 'write this .hex file to flash' is implemented in code that i had nothing to do with. as i recall, i ended up needing to make changes to about 3 lines of code outside of the area where i was working (adapter-bitbang.c). i would estimate that my contribution to pic32prog, in terms of the number of lines of code written or edited, is well under 10%.

cheers,
rob :-)

Page 2 of 2

Print this page

To reply to this topic, you need to log in.