OK, I've tried to figure this out (but please bear in mind that I'm an ARM newbie).
Freescale K20 chips seem to have FlexRAM (a piece of memory that can be used either as EEPROM or RAM). The configuration for this is stored at 0x400, 16 bytes total. Described in the K20 reference manual, page 503.
So I guess this (flashcfg) should be left in the ld file as-is, just move "flash" to 0xc00.
MCHCK support
Moderator: utzig
-
- Posts: 71
- Joined: Sat Aug 22, 2015 1:22 pm
Re: MCHCK support
Here's a patch (moves things in MK20DX128VLF5.ld past bootloader; adjusts Makefiles for MCHCK demos), to be applied to 3.0.1. Tested on a MCHCK with mk20dx128vlf5 chip, but not on the official mchck bootloader: I can't make that one compile into the allocated 3072 bytes (I can do it for mk20dx32vlf5 on linux with a patched old gcc "sat", but even that one does not make the code sufficiently compact for mk20dx128. Recent gcc releases make the resulting binary even bigger.)
So, I've used a "different" DFU bootloader from here. That one works well, and uses <=4096 bytes. So the application code should start at 0x1000 (instead of 0xc00).
Perhaps make the bootloader size as a define somewhere (Makefile?) and make sure that the ldscript will use whatever value is supplied?
So, I've used a "different" DFU bootloader from here. That one works well, and uses <=4096 bytes. So the application code should start at 0x1000 (instead of 0xc00).
Perhaps make the bootloader size as a define somewhere (Makefile?) and make sure that the ldscript will use whatever value is supplied?
Who is online
Users browsing this forum: No registered users and 19 guests