RE: Kinetis TWR-K60N512-KIT questions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

It works with ecos toolchain and gcc-4.6 with -mcpu=cortex-m4!
Great job Ilija.
My miktake was to put optimization flag to -O0 in global flags.
I will test your RAM configuration and give you feedbacks.
> Date: Tue, 3 May 2011 19:10:30 +0200
> From: ilijak@xxxxxxxxxxx
> To: ecos-discuss@xxxxxxxxxxxxxxxxxxx
> Subject: Re:  Kinetis TWR-K60N512-KIT questions
> On 03.05.2011 17:07, jjp jjp wrote:
> > Hi list,
> > Sorry for my slow answer... (other stuff and injury)
> Oh! I hope you are in good health now.
> > I find a way to flash a program with CodeWarrior 10.1 using OSJTAG.
> > I'm using standard ecos arm-eabi tools for this test.
> > I modify the target.ld (put flash_security section at 0x000004b0) because linker give me something like that:
> NOTE: flash_security *must* reside *exactly* at locations 0x400..0x40f
> otherwise the chip may lock (in worst case - permanently).
> > --
> > /home/kvm/dev/crosstool/arm-cortex-toolchain/bin/../lib/gcc/arm-eabi/4.3.2/../../../../arm-eabi/bin/ld: section .flash_security [00000400 -> 0000040f] overlaps section .kinetis_misc [00000008 -> 00000473]
> I wander what do you have in kinetis_misc that causes this overlap.
> Normally kinetis_misc stuff occupies up to cca 0x200. Is it HAL diag or
> some of your stuff? If it is HAL diag pse deselect it. (And I might
> consider removing this option from CDL).
> > /home/kvm/dev/crosstool/arm-cortex-toolchain/bin/../lib/gcc/arm-eabi/4.3.2/../../../../arm-eabi/bin/ld: hello-k60.elf: section .flash_security lma 0x400 overlaps previous sections
> [snip]
> > I'm using the kernel template.
> > Maybe I have forgotten something important.
> > Ilija can you give me your ecos.ecc to have same parameters as you?
> At the moment I am away on a trip so it will take a day or 2 for me to
> make ecc and test.
> FYI I am normally using default template either with or without enabling
> UART driver (/dev/ser3). "Hello world" should work. I have also tried
> RedBoot and kernel template. All without problems.
> I suggest you to try default configuration "as is" with default template
> and "Hello world". On serial port connect some terminal (I am using
> minicom) set to "38400 N 1" with no handshaking.
> > I will take a look to clock configuration.
> What clock configuration do you use?
> FYI in meantime I have placed updated version on Bugzilla. It
> incorporates SRAM startup.
> Note: Beware not to accidentally flash SRAM startup image since it has
> no flash_security section - Lock Up may happen.
> Regards
> Ilija
> --
> Before posting, please read the FAQ:
> and search the list archive:

Before posting, please read the FAQ:
and search the list archive:

[Linux Embedded]     [U-Boot V2]     [Linux Kernel]     [Linux MIPS]     [Linux ARM]     [Linux for the Blind]     [Linux Resources]     [Photo]     [Yosemite]     [ISDN Cause Codes]     [ECOS Home]

Add to Google Powered by Linux