From: Neil <picdude3@narwani.org>
To: Microcontroller discussion list - Public. <piclist@mit.edu>
Sender: "piclist-bounces@mit.edu" <piclist-bounces@mit.edu>
Date: Tue, 29 Sep 2020 20:48:25 -0700
Subject: [PIC] 18F...K22, K42, K40
Thread-Topic: [PIC] 18F...K22, K42, K40
Thread-Index: AdaW3h/ZZO3sjZ8PQqmd7h/gbNDBUQ==
Message-ID: <5F740009.9050802@narwani.org>
Reply-To: Microcontroller discussion list - Public. <piclist@mit.edu>
Accept-Language: en-US
X-MS-Exchange-Organization-SenderIdResult: Pass
X-MS-Exchange-Organization-PRD: mit.edu
X-MS-TNEF-Correlator:
received-spf: None (protection.outlook.com: narwani.org does not designate
	permitted sender hosts)
dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
 d=narwani.org	; s=default;
	h=Content-Transfer-Encoding:Content-Type:MIME-Version:Date:
	Message-ID:Subject:From:Reply-To:To:Sender:Cc:Content-ID:Content-Description:
	Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:
	In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:
	List-Post:List-Owner:List-Archive;
	bh=sAAf5YhEmUcn1GsDEvMbmUUTkDpK6lYt2LFn/iWOz/g=;
	b=OtSfCmq5FbKZdb3nz7yInUztCG
	0n5MND+2QNhXFRmdY2R6/VsziBFFkPQP0uJcbbwWcUrePSO7BD/RCkTjisvTp9CqbreneHDYnPCD2
	WpHao+bfeVSIDIR8VBz4dHEMY6AcAqxlLttaxll6DShuGPAqPDeb0Y/LVrJbAq6hnzj0WZTVh618P
	ZzkSNXuLLRhC/sJd//3bvbw98AjIdQsk/v8RAjwAKgNB+FUglnlSFO4ulOa18mb04NMuePWPxSxKL
	hnVua5hpWiG/yLLCoIY7O0/S/BelbaoT9TDIGaYwxKktU/9Hb5GKe8TDxPhtwJEduHBqn8Z21LLx/
	rV/b78TA==;
authentication-results: spf=none (sender IP is 68.65.123.241)
	smtp.mailfrom=narwani.org; mit.edu; dkim=pass (signature was verified)
	header.d=narwani.org;mit.edu; dmarc=bestguesspass action=none
	header.from=narwani.org;
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
	Thunderbird/38.5.0
errors-to: piclist-bounces@mit.edu
list-id: "Microcontroller discussion list - Public." <piclist.mit.edu>
list-post: <mailto:piclist@mit.edu>
x-beenthere: piclist@mit.edu
x-mailman-version: 2.1.6
x-source-args:
x-source-dir:
x-antiabuse: Sender Address Domain - narwani.org
x-source:
x-authenticated-sender: premium47.web-hosting.com: ca4@narwani.org
x-topics: [PIC]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Looking at doing a project for someone who chose the PIC18LF45K40.
I remember a few years ago when I moved from K22 to K42 (to get the=20
12-bit ADC), there was an issue with pre-initializing EEPROM data, but=20
IIRC that had to do with MPLABX (vs MPLAB) and not an issue with the chip.
I did some workaround with looking for a key value in a specific EEPROM=20
location and if not there, it went through an initialization routine.
Being able to set different configurations in the code (using #define),=20
which then set specific values in EEPROM made life much easier.

With the K40, looks like I'm forced to use MPLABX, though for a 3rd=20
party, I probably should suck up my hatred of MPLABX and use the newer=20
tools.

That said... anyone know if I can pre-initialize EEPROM from MPLABX=20
nowadays?
PS: I don't want to manually punch in values into MPLABX IPE.

Cheers,
-Neil.


--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.