We asked Microchip for the information. We are Microchip Approved Software Partners so we can ask for key information.
This information was the used to populate the PIckit parts database. ------ Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: [email protected] <[email protected]> on behalf of [email protected] <[email protected]> Sent: Sunday, October 23, 2022 3:35:36 PM To: jallib <[email protected]> Subject: Re: [jallib] HEF usage: One suggestion and one question Thanks all for those creative answers @Rob : Indeed, using one HEF location as an indicator to know if the settings have already been initialised or not was my fallback solution. As you explain (and I wasn't aware of that), if you do not receive the value in the XML from Microchip, you can not put that value in the include file.... unfortunately. About the discussion to deduce the offset by assuming the HEF size is always 128 bytes, that seems very risky to me. Furthermore, in the document Rob H linked, there are already a bunch of PIC's for which that size is not at all 128 bytes..... I do not know what data is included in the Microchip XML files, but how does the programmers (ICD, PicKit, ....) know how much HEF there is ? Or do they not at all make the difference between normal flash and HEF ? Seems weird to me (but I'm not an expert).... Enjoy your Sunday Daiv Le dimanche 23 octobre 2022 à 13:11:27 UTC+2, Rob Hamerling a écrit : Hi RobJ and others, My assumption that HEF-size is always 128 comes from: https://ww1.microchip.com/downloads/en/DeviceDoc/30010068G.pdf In the explanation colums it says: HEF: High–Endurance Flash 128B Non–volatile data storage with high–endurance 100k E/W cycles It doesn't say if it is always in the highest program address region. Searching all datasheets isn't the favorite aspect of my hobby.... As far as size of program memory concerns: the device file contain a "pragma code", but I cannot find in the docs if there is a companion built-in constant definition, for example like there is one for bank size: "CONST target_bank_size = cexpr". If such a constant doesn't exists yet it would be handy to add it to the compiler. Regards, RobH -- Rob Hamerling, Vianen, NL -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/61cdd53e-398c-4c2d-8786-2762984b7e3an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/61cdd53e-398c-4c2d-8786-2762984b7e3an%40googlegroups.com?utm_medium=email&utm_source=footer>. -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jallib/CWXP265MB25180CB26E850122514FB194F92F9%40CWXP265MB2518.GBRP265.PROD.OUTLOOK.COM.
