public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ilija Kocho <ilijak@siva.com.mk>
To: tangwei <tziang@hotmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] kinetis kwikstik's ecos trouble
Date: Tue, 26 Jun 2012 08:26:00 -0000	[thread overview]
Message-ID: <4FE97219.1060501@siva.com.mk> (raw)
In-Reply-To: <BAY163-W58CE4CFE3CAD3F3C8F415BC0E00@phx.gbl>

Hi

It may be a hardware issue, depends on how do you power Kwikstik and
what do you use for RS232 signals?

I would assume that you use TWR-SER or compatible 3.3V MAX chip.
Then if you power the Kwikstik through it's own USB the Vdd voltage will
be 2.8V due to drop on serial Schottky diode (see Kwikstik schematic).
It seems the output level is too low for 3.3 MAX chip and you won't see
output although the chip is working.

If you power through Tower elevator then Vdd is 3.3V and you'll see output.

I hope this helps.

Ilija

On 26.06.2012 08:39, tangwei wrote:
> Dear all,
>   redboot have run on my kwikstik ok, but I am not sure whether the ecos is OK, my steps is below:
> use the CVS version which contains freescale's kwikstik template,
> 1. use the default setting for kwikstik to get the "libtarget.a" and etc;2. build the examples from the ecos/examples/ ,such as hello.c ,twothreads.c ,simple-alarm.c
> use the command below
> /opt/ecos/gnutools/arm-eabi/bin/arm-eabi-gcc -g -D_ECOS -I ../../test/default_install/include/ simple-alarm.c -L ../../test/default_install/lib -Ttarget.ld -nostdlib
> and get the a.out file3. transfer a.out into .bin ,use command below
> /opt/ecos/gnutools/arm-eabi/bin/arm-eabi-objcopy  -O binary a.out simple-alarm.bin
> finally I get hello.bin,twothreads.bin, and simple-alarm.bin 
>
> 4.Then I use j-Link to download any of the three bin file , the UART have nothing output, by the way, the UART's software and hardware's setting are the same-38400 8N1,UART5, and the redboot works OK.Does the UART setting is OK, and can someone tell me where is the bug?
> Thanks
> ----------tangwei 		 	   		  
>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2012-06-26  8:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  6:19 [ECOS] kinetis kwikstik redboot trouble tangwei
2012-06-20  6:25 ` tangwei
2012-06-20 11:18 ` Ilija Kocho
2012-06-21  1:00   ` tangwei
2012-06-21  6:36     ` Ilija Kocho
2012-06-26  6:39       ` [ECOS] kinetis kwikstik's ecos trouble tangwei
2012-06-26  8:26         ` Ilija Kocho [this message]
2012-06-26  9:07           ` tangwei
2012-06-26 10:27         ` Ilija Kocho
2012-06-28  3:22           ` tangwei
2012-06-30 10:19             ` Ilija Kocho
2012-07-02  5:52               ` tangwei
2012-07-03  7:10                 ` Ilija Kocho
2012-07-06  1:01                   ` [ECOS] eCos for FujitSu's MB9B506(cortex-M3) tangwei
     [not found]                   ` <BAY163-W35405946B43D33AF82284DC0B80@phx.gbl>
2012-08-21  3:56                     ` [ECOS] RE: Troubles when develop app with Kwikstik tangwei
2012-08-27  6:53                     ` [ECOS] " Ilija Kocho
2012-09-07  3:29                       ` tangwei
2012-09-07  8:48                         ` Ilija Kocho
2012-06-28  3:23           ` [ECOS] kinetis kwikstik's ecos trouble tangwei

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=4FE97219.1060501@siva.com.mk \
    --to=ilijak@siva.com.mk \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=tziang@hotmail.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).