What needs to go in a PIC24 development board?

[david]

If you're doing a lot of prototyping or even limited production, I have found the bench top reflow ovens very effective.  They put the board through either a standard or custom reflow profile and do a very nice job of it.
https://www.aliexpress.com/item/1005002101042086.html?spm=a2g0o.productlist.main.3.4ed8TsZYTsZYT0&algo_pvid=2ad0df53-27c3-462f-b699-1b0e31231e2f&algo_exp_id=2ad0df53-27c3-462f-b699-1b0e31231e2f-1&pdp_npi=4%40dis%21NZD%21277.17%21277.17%21%21%21163.29%21163.29%21%402101fb0a17130067704856844efd27%2112000037225033565%21sea%21NZ%21916888149%21&curPageLogUid=GEPA9FHwBv0m&utparam-url=scene%3Asearch%7Cquery_from%3A

For pasting prototype boards it's hard to beat a pneumatic dispenser with a foot pedal.   Just load the syringe, select the right diameter needle, adjust the amount dispensed and go for it.
  https://www.aliexpress.com/item/4000785130294.html?spm=a2g0o.productlist.main.9.578651eaOLuXzE&algo_pvid=f57ca461-9d83-4707-b720-9947f44864f4&aem_p4p_detail=202404130416418992721019882280003698676&algo_exp_id=f57ca461-9d83-4707-b720-9947f44864f4-4&pdp_npi=4%40dis%21NZD%2187.16%2174.09%21%21%2151.35%2143.65%21%402103251317130070019108419e07e2%2112000018665302534%21sea%21NZ%21916888149%21&curPageLogUid=0uPGHRsf0wIT&utparam-url=scene%3Asearch%7Cquery_from%3A&search_p4p_id=202404130416418992721019882280003698676_1

I accept that these outlays are probably beyond the budget of a hobbyist but they should quickly pay for themselves for even a small business. 

Cheers,
David

[John Lawton]

Hi David,

great tips, many thanks. I have to confess I'm not very at home with SMT assembly, it's a matter of having to do it sometimes but my recent 'discovery' of using thick flux was very helpful on this board and of course having the right equipment would make it much easier I'm sure.

John

[JohnB]

@top204(Les)  Had a look at the MELabs U2 software.  I assume you want to get away from the PICKit UI although personally I can live it as I only use it infrequently to load the initial Bootloader software. I'll  put some ideas  together and get your feedback before spending too much time on it.  As for charging I can't see people paying for that, the contributions I have received from users of Positron Studio has been minimal and don't even cover the licensing costs of development tools.

[John Lawton]

Hi John,

another plan?

In the folder: "C:\Program Files (x86)\melabs Programmer\Additional Devices" there are all the 16bit support files that are hidden away there when meProg is installed.

According to the README file, just copy all of them across to the folder one above, i.e. the program root directory and the U2 programmer will then continue to work with those files & devices.

These *.epc files hold the key to supporting new devices, so if you can crack their internal code then new parts may be able to be programmed, extending the life of the U2 programmer, unless a firmware upgrade would be required in which case that is not expected to be forthcoming from MeLabs, sadly.

JohnL

[top204]

I've always found the EPIC program to be tidy and and clear to operate with its three windows. The central window for the main program for reading, writing, erasing, setups etc, and the two optional children windows to show/change the config fuses that will be used in the HEX file, and to show the contents of flash, EEPROM, config and ident memory etc...

Then when programming, a standard bar is shown, moving up until finished. When called from an IDE, it accpepts command line parameters, so all that needs doing is "press the program button". It is such a shame that it has been abandoned, because, to me, it has always been the best programmer out their to use since 1999 when I made my own EPIC programmer hardware on a breadboard and used the Beta software on it, via the parallel port. It is so simple and strightforward. Bloody silly expensive to buy!, but very good to use. Especially the USB U2 type.

It is something I was planning to do years ago, when I discovered microcohip had released the source code for the PICkit programmers, but never had the time, and it is/was written in dreadful C#.

[John Lawton]

Hi Les,

have you managed to program a dsPIC33EP128GP502 or similar with your U2, as I can't get mine to recognise the device when in the Amicus board and I don't know whether it's the programmer or the board (which looks fine)?

I assume I can use either pair PGEC1/PGED1 or PGEC3/PGED3 based on the 2mm header linking?

I may have to try this again in a plain breadboard, but I'm not hopeful.

I've noticed that there are issues with some of the 16bit PIC families having different ICSP pin allocations too. This would make the design of a more universal board more messy & complex.

And don't look at the dsPIC33CKxxxMC502 which has different /MCLR & power pins too...

John

[John Lawton]

As a last resort I've just tried tp ICSP the dsPIC33EP128GP502 in a minimalist breadboard and again my U2 programmer doesn't recognise the device, so it seems I'll have to look for another programmer.

This is rather disappointing, to say the least.

John

[trastikata]

Hello John,

PICkit3 works quite well with 16-bit pics, never had problems, except you have to pay attention to MPLABx IPE voltages, which it likes to switch on from time to time for no obvious reason.

[John Lawton]

Thanks, I've never owned a PICkit programmer and as I've just ordered a NSDSP-2-X from Northern Software - I probably never will

John

[top204]

I've never gotten up to the dsPIC33E type devices with the U2 programmer John. At the time of designing the PCB, they were still SMD types. The jumpers on the PCB need moving for the F, H and E types of PIC24 that were around then, because of their pinout differences.

[John Lawton]

Les, when you have a quiet moment, please look into your crystal ball and see what Microchip are going to come up with over the next few years, then I can accommodate the forthcoming devices if possible. It looks like the 33CK series are out though, so if uChip use that pinout in future then a different board may be required for them or a lot of links.

[kcsl]

The links could be replaced with a couple of rows of header pins. You can either use wire jumpers or a small PCB (or strip of perf board) to create personality plugs for the different configurations.

[John Lawton]

Hi Les,

I'm puzzled about one of the connectors on the old Amicus24.

What are J2 and link Q2 for please, see graphic. I'd like to omit it if it isn't needed.

John

[top204]

The back programming pins were to try and get some compatability with an Arduino board, because it uses the back block for SPI as well. That is why the jumper was there, but I cannot remember all the details now, because it has ben 10 years since I designed it. :-)

The Amicus24 was still in development and not actually a release, so I was just going to remove that and make the back pins as I did with Amicus18 and make them compatible for a PICkitX socket to plug directly into them.

[John Lawton]

Ah, many thanks. I think then I'll omit that 3x2 header as all PIC pins are available on the other headers anyway.

The PICkit type ICSP you fitted works fine, I have fitted the same but probably with the full 6 pins like the Amicus18 as my Northern Software programmer has just arrived - and I'm pleased to say it programs my dsPIC33EP - and that has all 6 pins too and I'd like to avoid mis-plugging.

I've added a QUIIC connector for I2C with links to select the hardware I2C port but I'll have to think about SPI. I don't know about a similar common connector/pinout type for SPI, Wikipedia suggests UEXT, Pmod, JTAG.... so many 'standards' as well as the Arduino one.

John

[JohnB]

On the subject of PICKitPlus, there is an alternative UI that Anobium have developed named PICKitEasy.  This has a simpler UI and might be less cumbersome to use than the PICKit app.

I have also discovered that it is possible to get the PK+ Command Line bootloader to append programming messages to the PBE file enabling these messages to appear in the Message are of the IDE.

I don't think there is much milage in developing another front end to PK+.