New Life For PICKIT 3 Stand Alone Programmer App?

[tumbleweed]

That PIC18F27Q43 looks like a nice part, with a 12-bit DAC

The DAC is 8-bits on the Q43. It's the ADC that's 12-bits (same as the K42).
The Q43 is similar to the K42, but has "more" peripherals (4 uarts, 3 NCO, 8 CLC, 16-bit PWM).

One nice thing about the Q43 is that the peripheral SFR registers are located at the bottom of memory in bank 0. On the K42 they're up at the very top, which puts them out of reach of the MOVFF instruction, and you have to use the new MOVFFL 3-word instruction to get at them (slower, more code).

It also tends to be a tad cheaper (and right now more available).

 

[upand_at_them]

The DAC is 8-bits on the Q43. It's the ADC that's 12-bits (same as the K42).

Woops, I misread the webpage in haste...was about to order some! Still a good chip to have.

 

[Nigel Goodwin]

The DAC is 8-bits on the Q43. It's the ADC that's 12-bits (same as the K42).
The Q43 is similar to the K42, but has "more" peripherals (4 uarts, 3 NCO, 8 CLC, 16-bit PWM).

The bewildering array of new devices and new peripherals is getting crazy There are often problems sourcing the devices though, I have to get my 42's from Farnell as RS don't stock them.

One nice thing about the Q43 is that the peripheral SFR registers are located at the bottom of memory in bank 0. On the K42 they're up at the very top, which puts them out of reach of the MOVFF instruction, and you have to use the new MOVFFL 3-word instruction to get at them (slower, more code).

It also tends to be a tad cheaper (and right now more available).

If you're using XC8 then it doesn't really matter, and for most new devices the examples tend to be in C rather than assembler.

 

[Nigel Goodwin]

Woops, I misread the webpage in haste...was about to order some! Still a good chip to have.

If you can get them, Farnell are saying lead time 358 days!

 

[upand_at_them]

The bewildering array of new devices and new peripherals is getting crazy

Just as crazy as the 1000-page datasheets with NO index, since they took over Atmel.

 

[tumbleweed]

If you're using XC8 then it doesn't really matter, and for most new devices the examples tend to be in C rather than assembler.

Well, it does still matter since accessing SFR's on the K42 can result in larger code and be slower.
If it's able to use the bank select register instead then it won't matter much (or if you don't care).

lead time?
Fugget about it. That's a constant game of Whack-A-Mole these days. If you're lucky enough to find ANY chips, buy 'em, cause they likely won't be there tomorrow.

 

[Mike - K8LH]

Just as crazy as the 1000-page datasheets with NO index, since they took over Atmel.

It doesn't have an index?

 

[Nigel Goodwin]

It doesn't have an index?

I downloaded one earlier today, and that has a table of contents same as most PDF datasheets.

 

[upand_at_them]

Once they acquired Atmel, or maybe it was a short time before that, the datasheets ballooned in size and dropped the index. Index is different than TOC. With an index you can quickly jump to a topic or register description.

 

[Nigel Goodwin]

Once they acquired Atmel, or maybe it was a short time before that, the datasheets ballooned in size and dropped the index. Index is different than TOC. With an index you can quickly jump to a topic or register description.

I don't recall ever seeing an index as such in MicroChip datasheets?, nor any particular need for one?.

 

[Ian Rogers]

Once they acquired Atmel, or maybe it was a short time before that, the datasheets ballooned in size and dropped the index. Index is different than TOC. With an index you can quickly jump to a topic or register description.

I like the Microchip datasheets..

If you half know the chip, I use the TOC to go to the "registers" page, then every register is hyperlinked.

I have really got used to these..

BUT!!!!! The pic 32 is an awful mess.. Each internal module is represented by its own datasheet... Nightmare!

 

[augustinetez]

Didn't even realise they had dropped the index, I use the bookmarks to get around.

Microchips datasheets are a case of whack-a-mole these days - if you are very, very lucky, you'll find one without any errors in it

 

[Nigel Goodwin]

if you are very, very lucky, you'll find one without any errors in it

Sorry, I don't believe you!

 

[Jon Wilder]

For a Windows front end you can probably leverage Visual Basic in Microsoft Visual Studio. Total drag & drop GUI design.

 

[Ian Rogers]

Is this aimed at this thread Jon??? Nowt todo with datasheet issues..

 

[Ian Rogers]

Sorry, I don't believe you!

Thats what addendums are for.... Of course there are errors... Written by man!!!!

 

[Nigel Goodwin]

Thats what addendums are for.... Of course there are errors... Written by man!!!!

The addendums (when they release any) often have errors as well

 

[upand_at_them]

Thought I'd add this...Happened upon it today.

https://github.com/jaromir-sukuba/a-p-prog

A project that uses an Arduino to program PICs. Looking at the device file it should be straightforward enough to add devices.

 

[Mike - K8LH]

I've been able to use a relatively inexpensive Arduino Nano clone to read/write/program 18FxxQ40, 18FxxQ41, and 18FxxQ43 devices in LVP (Low Voltage Programming) mode. Fun stuff but I could use a hand writing a Windows "front end" to manage file transfer to/from the Arduino.

For a Windows front end you can probably leverage Visual Basic in Microsoft Visual Studio. Total drag & drop GUI design.

Is this aimed at this thread Jon??? Nowt todo with datasheet issues..

I believe Jon was referring to a portion of my first post (thank you, Jon).

 

[Ian Rogers]

Apologies Jon... You know I can't read LOL... For a front end I would use Lazarus... No dependencies and can run without installing..