This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001395] LPC1766/LPC17XX .ldi file forgets about IAP RAM usageand NXP flash checksum
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: unassigned at bugs dot ecos dot sourceware dot org
- Date: Mon, 5 Dec 2011 09:00:39 +0000
- Subject: [Bug 1001395] LPC1766/LPC17XX .ldi file forgets about IAP RAM usageand NXP flash checksum
- Auto-submitted: auto-generated
- References: <bug-1001395-777@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001395
--- Comment #3 from Bernard Fouchà <bernard.fouche@kuantic.com> 2011-12-05 09:00:34 GMT ---
(In reply to comment #2)
> (In reply to comment #1)
>
> > (In reply to comment #0)
> >
> > > - if In Application Programming (IAP) is used, then the upper 32 bytes of
> > > internal RAM are used by the IAP built-in ROM. (section 32.3.2.8 of NXP
> > > document UM10360). This area is ignored in .ram definition.
> >
> > This could be fixed with appropriate patch to .ldi file. I think this should
> > be optional/configurable by a CDL option. But is it likely that IAP will be
> > used from eCos?
>
> Some LPC17xx parts have an external memory controller. IAP might then be used
> to store application data in the internal flash.
Any bootloader that writes into internal FLASH must use IAP: we have detected
this issue while writing an eCos based bootloader, even if we have no external
RAM on our target (LPC1765 has no external memory controller). Beside Ethernet,
there are CAN buses, UART, etc. that can be used to update the internal FLASH.
Thanks for the patch regarding the Valid User Code area!
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.