From: Ilija Kocho <ilijak@siva.com.mk>
To: "Linh Nguyễn" <nvl1109@gmail.com>
Cc: "Morris, Richard" <Richard.Morris@lifetech.com>,
eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: Redboot for Kinetis TWR-K70F120M
Date: Fri, 06 Jan 2012 12:30:00 -0000 [thread overview]
Message-ID: <4F06E93C.4030808@siva.com.mk> (raw)
In-Reply-To: <CAFUHsqYjXYU-WPaEtP4J3rKYJh_0RSD897RTJkXQRcJZ=-kReg@mail.gmail.com>
On 05.01.2012 11:38, Linh Nguyá»
n wrote:
> Hi all,
> Thanks for your replies. Currently, I don't understand about DDRAM of
> K70. Do I need configure DDRAM session in linker file, or doing
> somethings with DDRAM? K60 board does not have DDRAM, so where kernel
> will be loaded when booting?ote
You shall need linker script with a region and section for DDRAM indeed.
Also you will need some code for initialization of DDR controller and
possibly DDRAM chip.
Ilija
Little technical note: eCos mailing list filter permits only plain text
so your HTML formatted mail has been rejected. In order to pass through
instruct your e-mail client for plain text format when sending to eCos
mailing list.
>
> 2012/1/4 Morris, Richard <Richard.Morris@lifetech.com
> <mailto:Richard.Morris@lifetech.com>>
>
> Hi All,
>
> Regarding using J-Link and Ecos.
>
> I use J-Link with eCos and ARM processors. I have used it with
> the Kinetis K60, the NXP LPC2xxx family, Atmel AT91SAM family.
>
> My configuration is:
> Ubuntu Host 10.04
> Eclipse 3.6
> Zylin CDT Plugin (http://opensource.zylin.com/embeddedcdt.html)
> GCC compiler: provided with eCos or CodeSourcery's
> Segger's GDB Server (running on Linux or Windows)
> Segger's J-Link and/or J-Link Pro
>
> Regards,
>
> Richard
>
>
>
>
> On Jan 3, 2012, at 6:01 AM, Ilija Kocho wrote:
>
>> Hello Linh
>>
>> Thank you for your interest in eCos for Kinetis. First I would invite
>> you to post your comments and questions to some of eCos mailing
>> lists:
>> http://ecos.sourceware.org/intouch.html The benefit is both for
>> community and you, for instance I have no experience with J-Link, but
>> somebody else may have.
>>
>> Regarding your attempt to run eCos on K70, apparently you are luckier
>> than me :) as you already got a K70 tower.
>> I am waiting for my K70 tower so I haven't been able to play with
>> K70 so
>> far, but from K70 RM I can assume that variant HAL may need some
>> changes
>> (Clocking, etc.) in order to become compatible with K70.
>>
>> Regarding your code: I would avoid changing variant default settings,
>> you can achieve similar effect by stating requirements in
>> platform HAL,
>> Please look at K40 CDL.
>>
>> Regards
>> Ilija
>>
>>
>> On 03.01.2012 09:00, Linh Nguyá»
n wrote:
>>> Dear Kocho,
>>>
>>> Currently, I porting Redboot from TWR K60 to K70. I have used source
>>> code from http://hg-pub.ecoscentric.com/ecos/. The attach files are
>>> patch for TWR K70 and eCos config file for k70-redboot. Redboot for
>>> K70 can build, but it can not run after download by IAR workbench
>>> through J-Link. Can you spend some free times to get overview on it,
>>> then give me your comments please. Thanks so much and have nice
>>> week.
>>>
>>> I'm looking forward to hearing from you.
>>>
>>> Thanks & Regards,
>>> Linh Nguyen
>> --
>> Before posting, please read the FAQ:
>> http://ecos.sourceware.org/fom/ecos
>> and search the list archive:
>> http://ecos.sourceware.org/ml/ecos-discuss
>>
>
> Richard Morris
> *Senior Staff Firmware Engineer*
>
> *T* 650.638.6883
> 850 Lincoln Centre Dr
> MS 407-1
> Foster City, CA 94404
> USA
> http://www.lifetechnologies.com <http://www.lifetechnologies.com/>
>
>
>
> This email and its attachments are confidential. If you received
> this email in error, please notify the sender and delete.
>
>
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2012-01-06 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFUHsqaQs9Wdec7PNGtwn_dYxKd7genuCu=GvUEpELvEu+nVyA@mail.gmail.com>
2012-01-03 14:02 ` Ilija Kocho
[not found] ` <55EF8FF4-F78D-4B53-9E4F-4231F7A411BA@lifetech.com>
[not found] ` <CAFUHsqYjXYU-WPaEtP4J3rKYJh_0RSD897RTJkXQRcJZ=-kReg@mail.gmail.com>
2012-01-06 12:30 ` Ilija Kocho [this message]
2012-01-07 3:06 ` Linh Nguyễn
2012-01-07 9:45 ` Ilija Kocho
2012-01-07 10:35 ` Linh Nguyễn
2012-01-09 21:37 ` Ilija Kocho
2012-01-10 2:39 ` Linh Nguyễn
2012-01-10 8:04 ` Ilija Kocho
2012-02-02 8:55 ` Linh Nguyễn
2012-02-03 22:32 ` Ilija Kocho
2012-02-08 7:32 ` Linh Nguyễn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F06E93C.4030808@siva.com.mk \
--to=ilijak@siva.com.mk \
--cc=Richard.Morris@lifetech.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=nvl1109@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).