From: "David Duffy (AVD)" <david@audiovisualdevices.com.au>
To: Microcontroller discussion list - Public. <piclist@mit.edu>
Sender: "piclist-bounces@mit.edu" <piclist-bounces@mit.edu>
Date: Tue, 29 Sep 2020 21:22:57 -0700
Subject: Re: [PIC] 18F...K22, K42, K40
Thread-Topic: [PIC] 18F...K22, K42, K40
Thread-Index: AdaW53aGXPpAG9MgT3iFGl7YM8tBug==
Message-ID: <bde3c379-3c00-3c5a-70a3-3bcd0d30f2f0@audiovisualdevices.com.au>
References: <5F740009.9050802@narwani.org>
In-Reply-To: <5F740009.9050802@narwani.org>
Reply-To: Microcontroller discussion list - Public. <piclist@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-SenderIdResult: Pass
X-MS-Exchange-Organization-PRD: mit.edu
X-MS-TNEF-Correlator:
received-spf: Pass (protection.outlook.com: domain of
	audiovisualdevices.com.au designates 59.167.208.207 as permitted	sender)
	receiver=protection.outlook.com; client-ip=59.167.208.207;
	helo=lister.audiovisualdevices.com.au;
dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=mitprod.onmicrosoft.com; s=selector2-mitprod-onmicrosoft-com;
	h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
	bh=03NRPsUX1A9aaZTXUT5EEfPjDjaqD0HcgtVYuObWT1Q=;
	b=CyiJCPRir4w8s0VKqVxW2NTbZcKY2/nuKhjfA5ZGfzNyDkMpMRrXN8ESuuwJ+w2Z8jydpbbkLXiPundZf7bDQ9Gnl7moDWHpAoKG8k1kRBlVm0zUjdw62Li7tMA9tikyEnRM2uGzYLvZGrNf80uqG+MyXRrLLr4EkTb9FF3X3yc=
authentication-results: spf=pass (sender IP is 59.167.208.207)
	smtp.mailfrom=audiovisualdevices.com.au; mit.edu; dkim=none (message not
	signed) header.d=none;mit.edu; dmarc=bestguesspass action=none
	header.from=audiovisualdevices.com.au;
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0)
 Gecko/20100101	Thunderbird/68.12.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-spam-status: No, hits=-2.001 required=5 tests=ALL_TRUSTED, BAYES_00,
	NICE_REPLY_A, SUBJ_ALL_CAPS
x-virus-status: No
x-topics: [PIC]
x-mailman-approved-at: Wed, 30 Sep 2020 00:52:13 -0400
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

I've done it this way:

__EEPROM_DATA(0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00); // 0x00..0x0=
7

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 chip=
..
> 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
___________________________________________
David Duffy        Audio Visual Devices P/L
Unit 8, 10 Hook St, Capalaba 4157 Australia
Ph: +61 7 38235717      Fax: +61 7 38234717
Our Web Site: www.audiovisualdevices.com.au
___________________________________________

--=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
.