Hi list, Sorry for my slow answer... (other stuff and injury) 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: -- /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] /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 /home/kvm/dev/crosstool/arm-cortex-toolchain/bin/../lib/gcc/arm-eabi/4.3.2/../../../../arm-eabi/bin/ld: hello-k60.elf: section .ARM.exidx lma 0x410 overlaps previous sections /home/kvm/dev/crosstool/arm-cortex-toolchain/bin/../lib/gcc/arm-eabi/4.3.2/../../../../arm-eabi/bin/ld: hello-k60.elf: section .text lma 0x420 overlaps previous sections /home/kvm/dev/crosstool/arm-cortex-toolchain/bin/../lib/gcc/arm-eabi/4.3.2/../../../../arm-eabi/bin/ld: hello-k60.elf: section .rodata lma 0x67e0 overlaps previous sections /home/kvm/dev/crosstool/arm-cortex-toolchain/bin/../lib/gcc/arm-eabi/4.3.2/../../../../arm-eabi/bin/ld: hello-k60.elf: section .eh_frame lma 0x6a10 overlaps previous sections collect2: ld returned 1 exit status scons: *** [hello-k60.elf] Error 1 --
I flash a little blinking led exemple but apparently it stucks in clock configuration in hal_start_main_clock : -- 209 CYGHAL_KINETIS_MCG_WAIT_WHILE(!(mcg_p->S & CYGHWR_HAL_KINETIS_MCG_S_PLLST_M)); -- Backtrace seems to be strange: -- #0 hal_start_main_clock () at /home/kvm/dev/ecos-v3.0/ecos/packages/hal/cortexm/kinetis/var/current/src/kinetis_misc.c:197 #1 0x0000001a in hal_start_clocks () at /home/kvm/dev/ecos-v3.0/ecos/packages/hal/cortexm/kinetis/var/current/src/kinetis_misc.c:144 #2 0x00003b84 in Cyg_HardwareThread::thread_entry (thread=0x0) at /home/kvm/dev/ecos-v3.0/ecos/packages/kernel/current/src/common/thread.cxx:94 -- 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? I will take a look to clock configuration. Regards. ---------------------------------------- > From: jackoa...@hotmail.com > To: edgar.grimb...@gmail.com > CC: ecos-discuss@ecos.sourceware.org > Date: Thu, 14 Apr 2011 15:11:40 +0100 > Subject: RE: [ECOS] Kinetis TWR-K60N512-KIT questions > > > Hi, > I use finally SEGGER J-Flash program (4.2.4) to flash my bin. > But now with same program I can't access my board > (even a connection to it!) and I am trying to solve this situation. > > In OpenOCD doc, for Internal Flash it needs a driver name. > Except stm32 and at91sam3 which are cortex-m3 cores, there is nothing else. > > There is an USB-OSJTAG port on the board. Apparently CodeWarrior can access > it to program flash and if I can't solve my problem with J-Link I will test > it. > > Regards. > > ---------------------------------------- > > Date: Thu, 14 Apr 2011 15:17:53 +0200 > > From: edgar.grimb...@gmail.com > > To: jackoa...@hotmail.com > > CC: ecos-discuss@ecos.sourceware.org > > Subject: Re: [ECOS] Kinetis TWR-K60N512-KIT questions > > > > On Thu, Apr 14, 2011 at 2:14 PM, jjp jjp wrote: > > > > > > Hi, > > > Patchs apply! > > > (Date of last commit of my revison is Wed Apr 06 16:54:16 2011 +0000 with > > > with changeset 3029:9aec6a8ff9b92bcfff4852e47355e64494ec9ca8) > > > > > > I make a simple "Hello world" application. > > > I am trying to find a way to flash binary file from elf application using > > > CodeWarrior way. > > > > If you use OpenOCD (ZY1000 is OpenOCD), and you configure it > > correctly, you can flash from within GDB on a "load" command. > > Of course, you can transform your elf file into a bin (using objcopy), > > and then flash it using a flash programmer of sorts. > > What is the CoreWarrior way? > > > > Edgar > > > > > Are you using PEEDI to flash your application? > > > Regards. > > > > > > > > >> Date: Thu, 14 Apr 2011 12:52:59 +0200 > > >> From: ili...@siva.com.mk > > >> To: ecos-discuss@ecos.sourceware.org > > >> Subject: Re: [ECOS] Kinetis TWR-K60N512-KIT questions > > >> > > >> On 14.04.2011 09:28, jjp jjp wrote: > > >> > Hi, > > >> > I have a TWR-K60N512 too! > > >> > Is it possible to apply patchs to Mercurial version? > > >> > > >> Actually, our Kinetis port is not yet committed to CVS. It is in > > >> Bugzilla, in a queue for review by maintainers. > > >> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001187 > > >> You can download the Kinetis Port diff files from there and patch your > > >> eCos repository. Please observe the note (Comment 3) regarding patching. > > >> > > >> I recommend to checkout a fresh eCos repository from CVS/Mercurial > > >> unless you have revision later than 2011-04-06 17:59:20 BST, since it > > >> has resolved bugs 1001184, 1001186 which are needed for this port. > > >> > > >> I also recommend for first run to use official eCos gnutools. Later you > > >> can try gcc-4.6.0 > > >> > > >> Tell me if you need additional info. > > >> > > >> 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 > > >> > > > > > > > > > -- > > > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > > > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > > > > > > > > > > -- > > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > > > > > -- > Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos > and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss > -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss