From: Neil <picdude3@narwani.org>
To: Microcontroller discussion list - Public. <piclist@mit.edu>
Sender: "piclist-bounces@mit.edu" <piclist-bounces@mit.edu>
Date: Wed, 30 Sep 2020 07:43:28 -0700
Subject: Re: [PIC] 18F...K22, K42, K40
Thread-Topic: [PIC] 18F...K22, K42, K40
Thread-Index: AdaXObI7zNrXBk6nSUia49a5zCX3NA==
Message-ID: <5F749990.4070803@narwani.org>
References: <5F740009.9050802@narwani.org>
	<bde3c379-3c00-3c5a-70a3-3bcd0d30f2f0@audiovisualdevices.com.au>
In-Reply-To: <bde3c379-3c00-3c5a-70a3-3bcd0d30f2f0@audiovisualdevices.com.au>
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:In-Reply-To:
	MIME-Version:Date:Message-ID:From:Reply-To:To:References:Subject:Sender:Cc:
	Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
	Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:
	List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=ZRZoYWXxl1SlCg7dISPXYpyjnjm4keWpF6vUOn07+vI=;
	b=a17WLl9p5WiqYswnPEtpgpnQYA
	PX80BPc6OIIFB7+G8ImyLJurTyLnbWWCtQcPTJ52hzcy9OAwEJgXn4lC3gMqC7+61a+RLpGePFvrb
	EFjtZbP8o7RwPSSJ6VSOciAvVSTjRd7BLs/4tvbz++cUl1o1DOx/T84BIWP9/JPxxjA3qSJTB5q9W
	+KSiCUIhoWyDjeEfVd9lO4XW/4t2PlKJAkpfO+yHoepyL614jz8VHwg8LSB307lAREHGLqv/+iNow
	TjoKJS8y0lXsChNrbkoHjub/gi5xS123Vuhm0zvoeUyYey7He46aFuHGu9YQB6a47c8nWi9bfcBkN
	kKOEpmZA==;
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

I'm scratching my head trying to remember what the specific issue is=20
then, because I know of this... hmmm...
.... I'll go look at some old code.



On 9/30/2020 12:22 AM, David Duffy (AVD) wrote:
> I've done it this way:
>
> __EEPROM_DATA(0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00); // 0x00..0=
x07
>
> David...
>
> On 30/09/2020 1:48 pm, Neil wrote:
>> 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
>> 12-bit ADC), there was an issue with pre-initializing EEPROM data, but
>> IIRC that had to do with MPLABX (vs MPLAB) and not an issue with the chi=
p.
>> I did some workaround with looking for a key value in a specific EEPROM
>> location and if not there, it went through an initialization routine.
>> Being able to set different configurations in the code (using #define),
>> 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
>> party, I probably should suck up my hatred of MPLABX and use the newer
>> tools.
>>
>> That said... anyone know if I can pre-initialize EEPROM from MPLABX
>> 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
.