Home
JAQForum Ver 24.01
Log In or Join  
Active Topics
Local Time 21:27 11 Nov 2025 Privacy Policy
Jump to

Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me.

Forum Index : Microcontroller and PC projects : MPLABX IPE

Author Message
bigmik

Guru

Joined: 20/06/2011
Location: Australia
Posts: 2971
Posted: 07:15am 25 Aug 2018
Copy link to clipboard 
Print this post

Hi All,

I decided to `give away' my old PC I used for flashing my PICs etc. and installed MPLABX IPE onto my `new' i7 7700 w GTX 1060 Graphics card and 1TB EVO 970 m.2 SSD

I downloaded the latest (at the time Ver 4.2) and the first thing I noticed is that I couldnt pin it to the task bar (all my other programs I can).

Then I hate the font on the communication window but I cant find where to set that.

THEN I can flash Pic'170 fine (I supply power separately to the PIC) but when I attempted to flash the PIC16f1454 chips I got fails to detect device errors (never had this issue before).

I can overcome the PIC16f1454 problem by supplying power via the PK3 which I have never really had success with before..

So what has possibly changed?

Any ideas?

I hate having to have the shortcut on my desktop instead of my task bar (win 10 Home) It was upgraded from WIN 7-Pro but the old PC was as well but I now do not have it to check its version of Micky-Soft. And having to select power the device every time is a pain as well. (I know I can lock this but I dont want this with the '170).

Kind Regards,

MickEdited by bigmik 2018-08-26
Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<<
 
matherp
Guru

Joined: 11/12/2012
Location: United Kingdom
Posts: 10572
Posted: 07:33am 25 Aug 2018
Copy link to clipboard 
Print this post

  Quote  I couldnt pin it to the task bar (all my other programs I can).


Just tried it and it worked fine for me (dragged from the programs list to the task bar)

  Quote  but when I attempted to flash the PIC16f1454 chips I got fails to detect device errors (never had this issue before).


16(L)F1454(5) seem to be difficult to program with PicKit3 for reasons I don't understand. I always batch program then using a Micromite as per the instructions on Geoff's Microbridge page. Works perfectly everytime
 
WhiteWizzard
Guru

Joined: 05/04/2013
Location: United Kingdom
Posts: 2959
Posted: 08:17am 25 Aug 2018
Copy link to clipboard 
Print this post

One observation I have here is that whilst programming a PIC16(L)F1454/5 with a PICKIT3 and MPLAB using 'Power Target Circuit' then I find I have to take the supply voltage down a notch. This then works every time for me! Leaving it set to the default voltage value results in various error messages.

I put this down to voltage drops in cables. Not anything to do with BigMik's issue though!!



 
robert.rozee
Guru

Joined: 31/12/2012
Location: New Zealand
Posts: 2463
Posted: 01:37pm 25 Aug 2018
Copy link to clipboard 
Print this post

i believe the 1455 firmware on geoff's page may not be the most recent version, see this thread:
http://www.thebackshed.com/forum/forum_posts.asp?TID=10457

for programming 1455's i have a pickit3 set up permanently in 'Programmer-To-Go' mode with a pair of AA cells to power the 1455 (you still need 5v USB power only for the pickit3). just connect the 1455, and press the 'go' button on the pickit3. 10 seconds later the LEDs change colour and it is all done.

it is one of the few/only useful uses i've found for the pickit3


cheers,
rob :-)
 
bigmik

Guru

Joined: 20/06/2011
Location: Australia
Posts: 2971
Posted: 10:57pm 25 Aug 2018
Copy link to clipboard 
Print this post

GDay Lads, All,

@Robert,

Is the HEX in that ZIP (v118 + dS30) the one with the Bootloader (ie is ds30 the bootloader?)

I have been flashing ver 117 into any bridge chips I programmed.. I thought that was the latest..


I can create one of course by updating and then reading in the HEX..

@Peter & WW,

On the old box I NEVER had any issues with PIC16f1454..

I have 2 PK3 (actually I have a 3rd spare stored away), one is set for the PIC32MX170F256B and the other is set for PIC16f1454 so I don't have to wait for firmware flashing each time. I have a dedicated jig for the PIC16f1454 that is powered locally.. I cannot detect the chip when the jig is powered now..

Maybe its now time to setup a PIC32PROG jig.. I know at least that works well.

And I don't need 3GB of `glug' clogging up my PC..

The pin to task bar drives me crazy, I have tried running as administrator and all. But no go.

Kind Regards,

Mick



Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<<
 
robert.rozee
Guru

Joined: 31/12/2012
Location: New Zealand
Posts: 2463
Posted: 03:28am 26 Aug 2018
Copy link to clipboard 
Print this post

  bigmik said  
Is the HEX in that ZIP (v118 + dS30) the one with the Bootloader (ie is ds30 the bootloader?)


the zip file called:
2018-04-28_181224_1455_v1.18_inc_ds30.zip

contains the hex file:
v118 + dS30.hex

this .hex file is version 1.18 combined with the bootloader.

unfortunately it was so long ago that we produced these that i'm not even too sure how to recreate everything. i wrote the mmbasic updater (v118 w.loader4.bas) that talks to the bootloader and will update the 1455 application to 1.18, while peter wrote the mmbasic programmer that programs a .hex file (containing bootloader+application) into a completely blank 1455 with the aid of a 9v battery.

does this (sort of) answer your question?


cheers,
rob :-)
 
Print this page


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

The Back Shed's forum code is written, and hosted, in Australia.
© JAQ Software 2025