This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Kinetis TWR-K60N512-KIT questions
- From: Ilija Kocho <ilijak at siva dot com dot mk>
- To: ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 03 May 2011 19:10:30 +0200
- Subject: Re: [ECOS] Kinetis TWR-K60N512-KIT questions
- References: <SNT129-W416FC5E2D4ADAAB0F94CB4ADFE0@phx.gbl> <4D41EB2B.5080504@siva.com.mk> <SNT129-W29DA08015F0442D154694DADA70@phx.gbl> <4D9F6B61.705@siva.com.mk> <SNT129-W5405CAB49945C350910B32ADA80@phx.gbl> <4DA49538.60100@siva.com.mk> <SNT129-W6240E139CA5039E8120D1BADAA0@phx.gbl> <4DA5C749.2040706@siva.com.mk> <SNT129-W4466FCCDDA8570569F344AADAD0@phx.gbl> <4DA6D20B.7080908@siva.com.mk> <SNT129-W538FACFF5D72B03C1BB623ADAD0@phx.gbl>,<BANLkTinsuCtnuw3rt0kMiSZ9FXUuT3s9pw@mail.gmail.com>,<SNT129-W112F21A043369695047CF1ADAD0@phx.gbl> <SNT122-W25E5D81DF4EA2BFB3E88EFAD9E0@phx.gbl>
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: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss