#PIC18F45K50-I/MV Devkit

1 messages ยท Page 1 of 1 (latest)

regal lintel
#

are those 1206? maybe use a smaller one

#

also ESD protection on the USB is prob a good idea

#

and so is USB C

zinc roost
#

10mA through the led makes it pretty (annoying) bright

#

The LED_USB has 5v on it

#

Why power flag on MCLR?

white forge
#

Follow the datasheet on the reset pin of the pic18f45k50, I don't think this is how microchip shows it in the datasheet (I have not checked)

zinc roost
#

For example, it is recommended that the capacitor, C1, be isolated from the MCLR pin during programming and debugging operations by using a jumper (Figure 2-2). The jumper is replaced for normal run-time operations.

#

10uf is gigantic.. probably wrong

#

Should be 100nF

signal pine
# zinc roost Should be 100nF

damn... I will check on the datasheet again.

Seem like it should also be 100nF like those other C. But I remember now, I chose 10uF because I want the delay to be 100ms :

delay = R(Ohm) x C(uF)
10k x 10uF = 100ms

signal pine
signal pine
#

what I worried was the usb power part.. which failed in my earlier revision.

zinc roost
#

IF KiCAD does DRC error without it, maybe the pin mode on the MCLR pin is wrong (set to power input instead of bidir)

#

Or maybe the ICSP's MCLR pin is set to power input

signal pine
zinc roost
#

hm my default lib is set to passive

signal pine
#

can you show your pin functions table ?

#

Oh.. seem quite identical.

zinc roost
#

What KiCAD version?

signal pine
#

can you also capture your Reset part ?

#

I just upgraded 8.xx -> 9.0.0

#

It forced me to rewire some parts after migration also.

zinc roost
#

The builtin PIC device is not the same as yours

#

I only have PIC18F45K50_QFP

#

MCLR is an input pin on that device

signal pine
#

maybe, my custom part for PIC18F45K50 was wrong ?

#

here is what it say if I remove such thing

#

my custom-made part for 18F45K50 with MCLR as PowerInput

#

maybe I modify it into input ?

#

Now I remember, during KiCAD 8, I can't find lib for this mcu, so I made one.

But now on kiCAD 9.0.0, I found one in library and its MCLR was "input"

#

Seem fine after I changed the symbol. Will update back to my ref.

Thank man ! ๐Ÿ™
This bugged me for a while.

#

I hope it would be more readable & newbie friendly than not-up-to-date library on KiCAD default.

zinc roost
#

If you REALLY want to improve vs builtin, you could start using the alt function feature, so that pin direction could be selected project wise

signal pine
#

Oh, so we don't need to edit symbol everytime ?

#

I had to make my own symbol for such reason.

zinc roost
#

Well yea, but you should normally not need to customize symbols if they are done correct, but the new feature makes you do better DRC. But IO directions are also firmware dependant, so that would have to match the alt function you select.

#

If you make IOs default bidir and add alt modes supported by this chip (input, output, open drain, ...) the user could choose to use alt mode or not to identify odd cases like input only pins connected to bidir IO, wich would pass DRC today, but fail if you know the IO will be configured as input only.

signal pine
#

seem quite interesting

zinc roost
#

Any reason for not adding 3d models to all parts? Or are you very confident that they will fit?

signal pine
#

Some have extended fees like 3$ per part to assemble, need to make them all "basic" to avoid fees