[ECOS] kinetis kwikstik redboot trouble

[ECOS] kinetis kwikstik redboot trouble

[tangwei]

Dear all,    Have troubles with Kinetis kwikstik when use redboot RAM startup .    I am a freshman to eCos,below is the steps about my troubles:
1. use the last CVS-eCos build the redboot from the template with no changes,and get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use the J-link commander to download the redboot.bin in kwikstik' flash from address 0x00;4. reset kwikstik,the redboot can startup successful. now I want to try the RAM startup for redboot1. same as above's step 1, I only change the template's start-up option from ROM startup to SRAM startup,get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use minicom,after the kwikstik start successful from flash, and give the "RedBoot >" as below:        RedBoot(tm) bootstrap and debug environment [ROM]                                  Non-certified release, version UNKNOWN - built 10:12:01, Jun 14 2012                                                                                              Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009           Free Software Foundation, Inc.                                                     RedBoot is free software, covered by the eCos license, derived from the            GNU General Public License. You are welcome to change it and/or distribute         copies of it under certain conditions. Under the license terms, RedBoot's          source code and full license terms must have been made available to you.           Redboot comes with ABSOLUTELY NO WARRANTY.        Platform: Freescale KwikStik (Cortex-M4)                                           RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]                       RedBoot> 
4. in the minicom console, input command RedBoot > load -v -m ymodem,and then send the file redboot.bin from setp 2,  the trouble becomming , it can't send the redboot.bin correctly, 
the minicom send file's diaglog is below
+-----------[ymodem upload - Press CTRL-C to quit]------------+       |Sending: redboot.bin                                         |       |Ymodem sectors/kbytes sent:   0/ 0kRetry 0: NAK on sector    |       |Ymodem sectors/kbytes sent:   2/ 0kRetry 0: Cancelled        |       |                                                                       |       |Transfer incomplete                                                 |       |                                                             |     | READY: press any key to continue...                         |+-------------------------------------------------------------+   
after press any key,the console gives below:
RedBoot> load -v -m ymodem                                                     CUnrecognized image type: 0x20008000                                           xyzModem - CRC mode, 3(SOH)/0(STX)/0(CAN) packets, 3 retries                   RedBoot> 
That's all, can anybody please help me? Are there any steps I did above were wrong? ThanksOr could anyone give me the right steps to startup redboot from RAM? 		 	   		  

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

RE: [ECOS] kinetis kwikstik redboot trouble

[tangwei]

[-- Attachment #1: Type: text/plain, Size: 4639 bytes --]



please see the attached,thanks
----------------------------------------
> From: tziang@hotmail.com
> To: ecos-discuss@ecos.sourceware.org
> Date: Wed, 20 Jun 2012 14:19:15 +0800
> Subject: [ECOS] kinetis kwikstik redboot trouble
>
>
> Dear all,篓垄 篓垄篓垄Have troubles with Kinetis kwikstik when use redboot RAM startup .篓垄 篓垄篓垄I am a freshman to eCos,below is the steps about my troubles:
> 1. use the last CVS-eCos build the redboot from the template with no changes,and get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use the J-link commander to download the redboot.bin in kwikstik' flash from address 0x00;4. reset kwikstik,the redboot can startup successful.篓垄now I want to try the RAM startup for redboot1. same as above's step 1, I only change the template's start-up option from ROM startup to SRAM startup,get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use minicom,after the kwikstik start successful from flash, and give the "RedBoot >" as below:篓垄 篓垄篓垄篓垄 篓垄 RedBoot(tm) bootstrap and debug environment [ROM] 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄 篓垄 Non-certified release, version UNKNOWN - built 10:12:01, Jun 14 2012 篓垄 篓垄 篓垄 篓垄 篓垄篓垄篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄 篓垄 Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 篓垄 篓垄 篓垄篓垄篓垄 篓垄 Free Software Foundation, Inc. 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄篓垄 篓垄 RedBoot is free software, covered by the eCos license, derived from the 篓垄 篓垄 篓垄 篓垄篓垄 篓垄 GNU General Public License. You are welcome to change it and/or distribute 篓垄 篓垄篓垄篓垄 篓垄 copies of it under certain conditions. Under the license terms, RedBoot's 篓垄 篓垄 篓垄篓垄 篓垄 source code and full license terms must have been made available to you. 篓垄 篓垄 篓垄篓垄篓垄 篓垄 Redboot comes with ABSOLUTELY NO WARRANTY.篓垄 篓垄篓垄篓垄 篓垄 Platform: Freescale KwikStik (Cortex-M4) 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄篓垄 篓垄 RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available] 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄篓垄 篓垄 RedBoot>篓垄
> 4. in the minicom console, input command RedBoot > load -v -m ymodem,and then send the file redboot.bin from setp 2,篓垄 the trouble becomming , it can't send the redboot.bin correctly,篓垄
> the minicom send file's diaglog is below
> +-----------[ymodem upload - Press CTRL-C to quit]------------+ 篓垄 篓垄 篓垄篓垄|Sending: redboot.bin 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 | 篓垄 篓垄 篓垄篓垄|Ymodem sectors/kbytes sent: 篓垄 0/ 0kRetry 0: NAK on sector 篓垄 篓垄| 篓垄 篓垄 篓垄篓垄|Ymodem sectors/kbytes sent: 篓垄 2/ 0kRetry 0: Cancelled 篓垄 篓垄 篓垄 篓垄| 篓垄 篓垄 篓垄篓垄| 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 | 篓垄 篓垄 篓垄篓垄|Transfer incomplete 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 | 篓垄 篓垄 篓垄篓垄| 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 | 篓垄 篓垄篓垄| READY: press any key to continue... 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 |+-------------------------------------------------------------+ 篓垄篓垄
> after press any key,the console gives below:
> RedBoot> load -v -m ymodem 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄CUnrecognized image type: 0x20008000 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄xyzModem - CRC mode, 3(SOH)/0(STX)/0(CAN) packets, 3 retries 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄 篓垄篓垄RedBoot>篓垄
> That's all, can anybody please help me? Are there any steps I did above were wrong? ThanksOr could anyone give me the right steps to startup redboot from RAM?
>
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
>
 		 	   		  

[-- Attachment #2: troubles.txt --]
[-- Type: text/plain, Size: 3142 bytes --]

Dear all,
    
Have troubles with Kinetis kwikstik when use redboot RAM startup .
    
I am a freshman to eCos,below is the steps about my troubles:

1. use the last CVS-eCos build the redboot from the template with no changes,and get the redboot.elf;
2. use arm-eabi-objcopy to get the redboot.bin;
3. use the J-link commander to download the redboot.bin in kwikstik' flash from address 0x00;
4. reset kwikstik,the redboot can startup successful.
 
now I want to try the RAM startup for redboot
1. same as above's step 1, I only change the template's start-up option from ROM startup to SRAM startup,get the redboot.elf;
2. use arm-eabi-objcopy to get the redboot.bin;
3. use minicom,after the kwikstik start successful from flash, and give the "RedBoot >" as below:
    
    RedBoot(tm) bootstrap and debug environment [ROM]                              
    Non-certified release, version UNKNOWN - built 10:12:01, Jun 14 2012           
                                                                               
    Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009       
    Free Software Foundation, Inc.                                                 
    RedBoot is free software, covered by the eCos license, derived from the        
    GNU General Public License. You are welcome to change it and/or distribute     
    copies of it under certain conditions. Under the license terms, RedBoot's      
    source code and full license terms must have been made available to you.       
    Redboot comes with ABSOLUTELY NO WARRANTY.
    
    Platform: Freescale KwikStik (Cortex-M4)                                       
    RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]                   
    RedBoot> 

4. in the minicom console, input command RedBoot > load -v -m ymodem,and then send the file redboot.bin from setp 2,
  the trouble becomming , it can't send the redboot.bin correctly, 

the minicom send file's diaglog is below

+-----------[ymodem upload - Press CTRL-C to quit]------------+       
|Sending: redboot.bin                                         |       
|Ymodem sectors/kbytes sent:   0/ 0kRetry 0: NAK on sector    |       
|Ymodem sectors/kbytes sent:   2/ 0kRetry 0: Cancelled        |       
|                                                                       |       
|Transfer incomplete                                                 |       
|                                                             |     
| READY: press any key to continue...                         |
+-------------------------------------------------------------+   

after press any key,the console gives below:

RedBoot> load -v -m ymodem                                                     
CUnrecognized image type: 0x20008000                                           
xyzModem - CRC mode, 3(SOH)/0(STX)/0(CAN) packets, 3 retries                   
RedBoot> 

That's all, can anybody please help me? Are there any steps I did above were wrong? Thanks
Or could anyone give me the right steps to startup redboot from RAM?

[-- Attachment #3: Type: text/plain, Size: 148 bytes --]

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

Re: [ECOS] kinetis kwikstik redboot trouble

[Ilija Kocho]

Hi Tangwei

The SRAM startup is not intended for loading with Redboot, but for JTAG
or alike. You can upload it (the elf file) with J-link.

Regards
Ilija


On 20.06.2012 08:19, tangwei wrote:
> Dear all,    Have troubles with Kinetis kwikstik when use redboot RAM startup .    I am a freshman to eCos,below is the steps about my troubles:
> 1. use the last CVS-eCos build the redboot from the template with no changes,and get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use the J-link commander to download the redboot.bin in kwikstik' flash from address 0x00;4. reset kwikstik,the redboot can startup successful. now I want to try the RAM startup for redboot1. same as above's step 1, I only change the template's start-up option from ROM startup to SRAM startup,get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use minicom,after the kwikstik start successful from flash, and give the "RedBoot >" as below:        RedBoot(tm) bootstrap and debug environment [ROM]                                  Non-certified release, version UNKNOWN - built 10:12:01, Jun 14 2012                                                                                              Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009           Free Software Foundation, Inc.                                                     RedBoot is free software, covered by the eCos license, derived from the            GNU General Public License. You are welcome to change it and/or distribute         copies of it under certain conditions. Under the license terms, RedBoot's          source code and full license terms must have been made available to you.           Redboot comes with ABSOLUTELY NO WARRANTY.        Platform: Freescale KwikStik (Cortex-M4)                                           RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]                       RedBoot> 
> 4. in the minicom console, input command RedBoot > load -v -m ymodem,and then send the file redboot.bin from setp 2,  the trouble becomming , it can't send the redboot.bin correctly, 
> the minicom send file's diaglog is below
> +-----------[ymodem upload - Press CTRL-C to quit]------------+       |Sending: redboot.bin                                         |       |Ymodem sectors/kbytes sent:   0/ 0kRetry 0: NAK on sector    |       |Ymodem sectors/kbytes sent:   2/ 0kRetry 0: Cancelled        |       |                                                                       |       |Transfer incomplete                                                 |       |                                                             |     | READY: press any key to continue...                         |+-------------------------------------------------------------+   
> after press any key,the console gives below:
> RedBoot> load -v -m ymodem                                                     CUnrecognized image type: 0x20008000                                           xyzModem - CRC mode, 3(SOH)/0(STX)/0(CAN) packets, 3 retries                   RedBoot> 
> That's all, can anybody please help me? Are there any steps I did above were wrong? ThanksOr could anyone give me the right steps to startup redboot from RAM? 		 	   		  
>



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

RE: [ECOS] kinetis kwikstik redboot trouble

[tangwei]

Thanks,Ilija
but I still have a question.
Does it means if I want to write a driver for kwikstik,I MUST write codes included in the redboot,then download redboot into kwikstik to see if the driver can work?
Are there some methods to download the image(include the driver's code) into RAM then debug not the Flash, you know the Flash have limited write cycles.    

----------------------------------------
> Date: Wed, 20 Jun 2012 13:18:35 +0200
> From: ilijak@siva.com.mk
> To: tziang@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] kinetis kwikstik redboot trouble
>
> Hi Tangwei
>
> The SRAM startup is not intended for loading with Redboot, but for JTAG
> or alike. You can upload it (the elf file) with J-link.
>
> Regards
> Ilija
>
>
> On 20.06.2012 08:19, tangwei wrote:
> > Dear all, Have troubles with Kinetis kwikstik when use redboot RAM startup . I am a freshman to eCos,below is the steps about my troubles:
> > 1. use the last CVS-eCos build the redboot from the template with no changes,and get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use the J-link commander to download the redboot.bin in kwikstik' flash from address 0x00;4. reset kwikstik,the redboot can startup successful. now I want to try the RAM startup for redboot1. same as above's step 1, I only change the template's start-up option from ROM startup to SRAM startup,get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use minicom,after the kwikstik start successful from flash, and give the "RedBoot >" as below: RedBoot(tm) bootstrap and debug environment [ROM] Non-certified release, version UNKNOWN - built 10:12:01, Jun 14 2012 Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. RedBoot is free software, covered by the eCos license, derived from the GNU General Public License. You are welcome to change it and/or distribute copies of it under certain conditions. Under the license terms, RedBoot's source code and full license terms must have been made available to you. Redboot comes with ABSOLUTELY NO WARRANTY. Platform: Freescale KwikStik (Cortex-M4) RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available] RedBoot>
> > 4. in the minicom console, input command RedBoot > load -v -m ymodem,and then send the file redboot.bin from setp 2, the trouble becomming , it can't send the redboot.bin correctly,
> > the minicom send file's diaglog is below
> > +-----------[ymodem upload - Press CTRL-C to quit]------------+ |Sending: redboot.bin | |Ymodem sectors/kbytes sent: 0/ 0kRetry 0: NAK on sector | |Ymodem sectors/kbytes sent: 2/ 0kRetry 0: Cancelled | | | |Transfer incomplete | | | | READY: press any key to continue... |+-------------------------------------------------------------+
> > after press any key,the console gives below:
> > RedBoot> load -v -m ymodem CUnrecognized image type: 0x20008000 xyzModem - CRC mode, 3(SOH)/0(STX)/0(CAN) packets, 3 retries RedBoot>
> > That's all, can anybody please help me? Are there any steps I did above were wrong? ThanksOr could anyone give me the right steps to startup redboot from RAM?
> >
>
>
>
> --
> 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

Re: [ECOS] kinetis kwikstik redboot trouble

[Ilija Kocho]

On 21.06.2012 03:00, tangwei wrote:
> Thanks,Ilija
> but I still have a question.
> Does it means if I want to write a driver for kwikstik,I MUST write codes included in the redboot,then download redboot into kwikstik to see if the driver can work?

No, you don't need Redboot for that. You can produce your own
application. Look at the examples.


> Are there some methods to download the image(include the driver's code) into RAM then debug not the Flash, you know the Flash have limited write cycles.    

That's determined by startup type. ROM is for flashing and SRAM is for
loading and debugging in SRAM. Typically you just submit the ELF file to
the debugger. Regarding flash writing limitations from my experience I
can tell that you will have a long time of development before you damage
the flash by cycling.

Note: Be careful not to flash SRAM startup image. That will put some
"random" value in Flash configuration field (0x400 - 0x40f) that may
lock the device. This lock may be permanent.

Ilija

>
> ----------------------------------------
>> Date: Wed, 20 Jun 2012 13:18:35 +0200
>> From: ilijak@siva.com.mk
>> To: tziang@hotmail.com
>> CC: ecos-discuss@ecos.sourceware.org
>> Subject: Re: [ECOS] kinetis kwikstik redboot trouble
>>
>> Hi Tangwei
>>
>> The SRAM startup is not intended for loading with Redboot, but for JTAG
>> or alike. You can upload it (the elf file) with J-link.
>>
>> Regards
>> Ilija
>>
>>
>> On 20.06.2012 08:19, tangwei wrote:
>>> Dear all, Have troubles with Kinetis kwikstik when use redboot RAM startup . I am a freshman to eCos,below is the steps about my troubles:
>>> 1. use the last CVS-eCos build the redboot from the template with no changes,and get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use the J-link commander to download the redboot.bin in kwikstik' flash from address 0x00;4. reset kwikstik,the redboot can startup successful. now I want to try the RAM startup for redboot1. same as above's step 1, I only change the template's start-up option from ROM startup to SRAM startup,get the redboot.elf;2. use arm-eabi-objcopy to get the redboot.bin;3. use minicom,after the kwikstik start successful from flash, and give the "RedBoot >" as below: RedBoot(tm) bootstrap and debug environment [ROM] Non-certified release, version UNKNOWN - built 10:12:01, Jun 14 2012 Copyright (C) 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. RedBoot is free software, covered by the eCos license, derived from the GNU General Public License. You are welcome to change it and/or distribute copies of it under certain conditions. Under the license terms, RedBoot's source code and full license terms must have been made available to you. Redboot comes with ABSOLUTELY NO WARRANTY. Platform: Freescale KwikStik (Cortex-M4) RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available] RedBoot>
>>> 4. in the minicom console, input command RedBoot > load -v -m ymodem,and then send the file redboot.bin from setp 2, the trouble becomming , it can't send the redboot.bin correctly,
>>> the minicom send file's diaglog is below
>>> +-----------[ymodem upload - Press CTRL-C to quit]------------+ |Sending: redboot.bin | |Ymodem sectors/kbytes sent: 0/ 0kRetry 0: NAK on sector | |Ymodem sectors/kbytes sent: 2/ 0kRetry 0: Cancelled | | | |Transfer incomplete | | | | READY: press any key to continue... |+-------------------------------------------------------------+
>>> after press any key,the console gives below:
>>> RedBoot> load -v -m ymodem CUnrecognized image type: 0x20008000 xyzModem - CRC mode, 3(SOH)/0(STX)/0(CAN) packets, 3 retries RedBoot>
>>> That's all, can anybody please help me? Are there any steps I did above were wrong? ThanksOr could anyone give me the right steps to startup redboot from RAM?
>>>
>>
>>
>> --
>> 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

[ECOS] kinetis kwikstik's ecos trouble

[tangwei]

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

Re: [ECOS] kinetis kwikstik's ecos trouble

[Ilija Kocho]

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

RE: [ECOS] kinetis kwikstik's ecos trouble

[tangwei]

Thanks,
but why my redboot work successfully,from the same UART and the same setting,
and I want to confirm If the example(hello.c,serial.c)use the kwikstik's UART5 for output,and the setting is 38400 8N1



----------------------------------------
> Date: Tue, 26 Jun 2012 10:26:01 +0200
> From: ilijak@siva.com.mk
> To: tziang@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] kinetis kwikstik's ecos trouble
>
> 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
>
 		 	   		  

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

Re: [ECOS] kinetis kwikstik's ecos trouble

[Ilija Kocho]

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

This command line isn't correct. Should contain flags: -mthumb
-mcpu=cortex-m3 (if you are using gcc-4.6 or newer you can also put
-mcpu=cortex-m4)
Recommended: -O2

I recommend you, as a template, to use the Makefile provided with examples.

I hope this helps.

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

RE: [ECOS] kinetis kwikstik's ecos trouble

[tangwei]

Thanks, I have used the Makefile provided with examples,now they can run successfully.
but when I want to try a example,I must use J-LINK to download the binfile into kwikstik's flash.
Is there any easy methods to do this by the redboot,such as use the redboot's load command,
first load the file into RAM,then use the redboot's go command to execute the example app,
if the app work successfully,then use J-LINK to download into flash.
I have try this way,setp1. download redboot ROM startup for Kwikstik,and get the below info when redboot startup
Platform: Freescale KwikStik (Cortex-M4)                                       RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available] 
step2. download the example app twothreads.bin,use
RedBoot> load -v -m ymodem                                                     CCUnrecognized image type: 0x20008000                                          xyzModem - CRC mode, 4(SOH)/0(STX)/0(CAN) packets, 4 retries 
then tryRedBoot> load -r -m ymodem -b 0x1fffb6a8                                       CRaw file loaded 0x1fffb6a8-0x20000ae7, assumed entry at 0x1fffb6a8            xyzModem - CRC mode, 172(SOH)/0(STX)/0(CAN) packets, 4 retries                 RedBoot> go -c 0x1fffb6a8                                                                   $T050f:a8b6ff1f;0d:e86f0020;#5c
both seems fail
 ----------------------------------------
> Date: Tue, 26 Jun 2012 12:26:44 +0200
> From: ilijak@siva.com.mk
> To: tziang@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] kinetis kwikstik's ecos trouble
>
> 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
>
> This command line isn't correct. Should contain flags: -mthumb
> -mcpu=cortex-m3 (if you are using gcc-4.6 or newer you can also put
> -mcpu=cortex-m4)
> Recommended: -O2
>
> I recommend you, as a template, to use the Makefile provided with examples.
>
> I hope this helps.
>
> 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

RE: [ECOS] kinetis kwikstik's ecos trouble

[tangwei]

----------------------------------------
> Date: Tue, 26 Jun 2012 12:26:44 +0200
> From: ilijak@siva.com.mk
> To: tziang@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] kinetis kwikstik's ecos trouble
>
> 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
>
> This command line isn't correct. Should contain flags: -mthumb
> -mcpu=cortex-m3 (if you are using gcc-4.6 or newer you can also put
> -mcpu=cortex-m4)
> Recommended: -O2
>
> I recommend you, as a template, to use the Makefile provided with examples.
>
> I hope this helps.
>
> 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

Re: [ECOS] kinetis kwikstik's ecos trouble

[Ilija Kocho]

On 28.06.2012 05:22, tangwei wrote:
> Thanks, I have used the Makefile provided with examples,now they can run successfully.
> but when I want to try a example,I must use J-LINK to download the binfile into kwikstik's flash.
> Is there any easy methods to do this by the redboot,such as use the redboot's load command,
> first load the file into RAM,then use the redboot's go command to execute the example app,
> if the app work successfully,then use J-LINK to download into flash.
> I have try this way,setp1. download redboot ROM startup for Kwikstik,and get the below info when redboot startup
> Platform: Freescale KwikStik (Cortex-M4)                                       RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available] 
> step2. download the example app twothreads.bin,use
> RedBoot> load -v -m ymodem                                                     CCUnrecognized image type: 0x20008000                                          xyzModem - CRC mode, 4(SOH)/0(STX)/0(CAN) packets, 4 retries 
> then tryRedBoot> load -r -m ymodem -b 0x1fffb6a8                                       CRaw file loaded 0x1fffb6a8-0x20000ae7, assumed entry at 0x1fffb6a8            xyzModem - CRC mode, 172(SOH)/0(STX)/0(CAN) packets, 4 retries                 RedBoot> go -c 0x1fffb6a8                                                                   $T050f:a8b6ff1f;0d:e86f0020;#5c
> both seems fail

There are 2 issues:

1. With Redboot you should load the elf file rather bin.

2. I assume you are using SRAM startup type for twothreads and it's not
intended for loading with Redboot. You should instead use J-link with
some GDB server. OpenOCD is known to work.

I hope this helps

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

RE: [ECOS] kinetis kwikstik's ecos trouble

[tangwei]

Dear ilijak
for your advise:
> 1. With Redboot you should load the elf file rather bin
If I use the redboot ROM startup for kwikstik, after redboot startup can I download the example app,such as hello.elf into the kwikstik's RAM,
and then use the redboot's go command to execute the app? 
If above can work,can you give me the correct command,thanks a lot.



----------------------------------------
> Date: Sat, 30 Jun 2012 12:19:05 +0200
> From: ilijak@siva.com.mk
> To: tziang@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: Re: [ECOS] kinetis kwikstik's ecos trouble
>
> On 28.06.2012 05:22, tangwei wrote:
> > Thanks, I have used the Makefile provided with examples,now they can run successfully.
> > but when I want to try a example,I must use J-LINK to download the binfile into kwikstik's flash.
> > Is there any easy methods to do this by the redboot,such as use the redboot's load command,
> > first load the file into RAM,then use the redboot's go command to execute the example app,
> > if the app work successfully,then use J-LINK to download into flash.
> > I have try this way,setp1. download redboot ROM startup for Kwikstik,and get the below info when redboot startup
> > Platform: Freescale KwikStik (Cortex-M4) RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]
> > step2. download the example app twothreads.bin,use
> > RedBoot> load -v -m ymodem CCUnrecognized image type: 0x20008000 xyzModem - CRC mode, 4(SOH)/0(STX)/0(CAN) packets, 4 retries
> > then tryRedBoot> load -r -m ymodem -b 0x1fffb6a8 CRaw file loaded 0x1fffb6a8-0x20000ae7, assumed entry at 0x1fffb6a8 xyzModem - CRC mode, 172(SOH)/0(STX)/0(CAN) packets, 4 retries RedBoot> go -c 0x1fffb6a8 $T050f:a8b6ff1f;0d:e86f0020;#5c
> > both seems fail
>
> There are 2 issues:
>
> 1. With Redboot you should load the elf file rather bin.
>
> 2. I assume you are using SRAM startup type for twothreads and it's not
> intended for loading with Redboot. You should instead use J-link with
> some GDB server. OpenOCD is known to work.
>
> I hope this helps
>
> 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

Re: [ECOS] kinetis kwikstik's ecos trouble

[Ilija Kocho]

On 02.07.2012 07:51, tangwei wrote:
> Dear ilijak
> for your advise:
>> 1. With Redboot you should load the elf file rather bin
> If I use the redboot ROM startup for kwikstik, after redboot startup can I download the example app,such as hello.elf into the kwikstik's RAM,
> and then use the redboot's go command to execute the app? 

You can't do it if your application startup type is SRAM. You will need
something like RAM startup (look TWR-K70F120M for example) but with
internal SRAM instead of external RAM. But then I'm afraid that there
will be very little memory for application.

> If above can work,can you give me the correct command,thanks a lot.

The only thing I can recommend, considering SRAM limitation is to use
J-link with some GDB server, such as OpenOCD.

Ilija

>
>
>
> ----------------------------------------
>> Date: Sat, 30 Jun 2012 12:19:05 +0200
>> From: ilijak@siva.com.mk
>> To: tziang@hotmail.com
>> CC: ecos-discuss@ecos.sourceware.org
>> Subject: Re: [ECOS] kinetis kwikstik's ecos trouble
>>
>> On 28.06.2012 05:22, tangwei wrote:
>>> Thanks, I have used the Makefile provided with examples,now they can run successfully.
>>> but when I want to try a example,I must use J-LINK to download the binfile into kwikstik's flash.
>>> Is there any easy methods to do this by the redboot,such as use the redboot's load command,
>>> first load the file into RAM,then use the redboot's go command to execute the example app,
>>> if the app work successfully,then use J-LINK to download into flash.
>>> I have try this way,setp1. download redboot ROM startup for Kwikstik,and get the below info when redboot startup
>>> Platform: Freescale KwikStik (Cortex-M4) RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]
>>> step2. download the example app twothreads.bin,use
>>> RedBoot> load -v -m ymodem CCUnrecognized image type: 0x20008000 xyzModem - CRC mode, 4(SOH)/0(STX)/0(CAN) packets, 4 retries
>>> then tryRedBoot> load -r -m ymodem -b 0x1fffb6a8 CRaw file loaded 0x1fffb6a8-0x20000ae7, assumed entry at 0x1fffb6a8 xyzModem - CRC mode, 172(SOH)/0(STX)/0(CAN) packets, 4 retries RedBoot> go -c 0x1fffb6a8 $T050f:a8b6ff1f;0d:e86f0020;#5c
>>> both seems fail
>> There are 2 issues:
>>
>> 1. With Redboot you should load the elf file rather bin.
>>
>> 2. I assume you are using SRAM startup type for twothreads and it's not
>> intended for loading with Redboot. You should instead use J-link with
>> some GDB server. OpenOCD is known to work.
>>
>> I hope this helps
>>
>> 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

[ECOS] eCos for FujitSu's MB9B506(cortex-M3)

[tangwei]

Dear all,
    Is there anyone have port eCos to FujitSu's MB9B506,
Thanks.
 		 	   		  

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

[ECOS] RE: Troubles when develop app with Kwikstik

[tangwei]

Dear all,

    I have a FreeScale's Kwikstik board,and have troubles when develop with it as below

setp1:Use the default redboot setting for KwikStik,and then download the bin into the flash,
then connect the COM,I get the below string on the computer,it seems the redboot is OK.

Platform: Freescale KwikStik (Cortex-M4)                                       
RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]                   
RedBoot> 

step2:Prepare the app from the examples directory (ELF fomart)
If I use the default kernel setting(the startup setting is ROM),build the examples with the kernel,
get the hello(elf fomart).
then use the gdb tool download the hello
(gdb) set remotebaud 38400
(gdb) target remote /dev/ttyUSB0
Remote debugging using /dev/ttyUSB0
0x00003aa2 in ?? ()
(gdb) load hello
Loading section .rom_vectors, size 0x8 lma 0x0
Load failed
(gdb) 

if I use the starup setting SRAM for the kernel,then do as above

(gdb) set remotebaud 38400
(gdb) target remote /dev/ttyUSB0
Remote debugging using /dev/ttyUSB0
0x00003aa2 in ?? ()
(gdb) load hello
Loading section .rom_vectors, size 0x8 lma 0x1fff8400
Loading section .ARM.exidx, size 0x10 lma 0x1fff8408
Loading section .text, size 0x4dbc lma 0x1fff8418
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...
Ignoring packet error, continuing...

I want to download the app to the RAM for debug,so I think the second kernel startup setting is right,
but I don't know somewhere else to make the change,
can anyone help me,where is the bug, and how to debug?

Thanks.




 		 	   		  

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

[ECOS] Re: Troubles when develop app with Kwikstik

[Ilija Kocho]

On 21.08.2012 05:52, tangwei wrote:
> Dear all,
>
> I have a FreeScale's Kwikstik board,and have troubles when develop
> with it as below
>
> setp1:Use the default redboot setting for KwikStik,and then download
> the bin into the flash,
> then connect the COM,I get the below string on the computer,it seems
> the redboot is OK.
>
> Platform: Freescale KwikStik (Cortex-M4)
> RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]
> RedBoot>
>
> step2:Prepare the app from the examples directory (ELF fomart)
> If I use the default kernel setting(the startup setting is ROM),build
> the examples with the kernel,
> get the hello(elf fomart).
> then use the gdb tool download the hello
> (gdb) set remotebaud 38400
> (gdb) target remote /dev/ttyUSB0
> Remote debugging using /dev/ttyUSB0
> 0x00003aa2 in ?? ()
> (gdb) load hello
> Loading section .rom_vectors, size 0x8 lma 0x0
> Load failed
> (gdb)
>

You can't load ROM startup with RedBoot. There is an experimental FLASH
startup
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623 that will enable
loading applications in Flash by means of Internal Flash driver
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001561 . With these you
should be able to load and run application, but GDB usage is limited
because current GDB stub doesn't support hardware breakpoints.

> if I use the starup setting SRAM for the kernel,then do as above
>
> (gdb) set remotebaud 38400
> (gdb) target remote /dev/ttyUSB0
> Remote debugging using /dev/ttyUSB0
> 0x00003aa2 in ?? ()
> (gdb) load hello
> Loading section .rom_vectors, size 0x8 lma 0x1fff8400
> Loading section .ARM.exidx, size 0x10 lma 0x1fff8408
> Loading section .text, size 0x4dbc lma 0x1fff8418
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
>
> I want to download the app to the RAM for debug,so I think the second
> kernel startup setting is right,
> but I don't know somewhere else to make the change,
> can anyone help me,where is the bug, and how to debug?
>

SRAM startup is not intended for use with Redboot but with JTAG. You can
use OpenOCD or J-Link.

I hope this helps.

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

RE: [ECOS] Re: Troubles when develop app with Kwikstik

[tangwei]

Dear Ilija,

you said

> SRAM startup is not intended for use with Redboot but with JTAG. You can
> use OpenOCD or J-Link.

but I found many examples in the net,which use Redboot(ROM startup burn into the on-chip flash)to debug the RAM startup APP(elf fomat) by the gdb com connect style not JTAG.

steps are same as I have mentioned below. Do you mean only the Kwikstik not support this debug style? Thanks



----------------------------------------
> Date: Mon, 27 Aug 2012 08:52:48 +0200
> From: ilijak@siva.com.mk
> To: tziang@hotmail.com
> CC: ecos-discuss@ecos.sourceware.org
> Subject: [ECOS] Re: Troubles when develop app with Kwikstik
>
> On 21.08.2012 05:52, tangwei wrote:
> > Dear all,
> >
> > I have a FreeScale's Kwikstik board,and have troubles when develop
> > with it as below
> >
> > setp1:Use the default redboot setting for KwikStik,and then download
> > the bin into the flash,
> > then connect the COM,I get the below string on the computer,it seems
> > the redboot is OK.
> >
> > Platform: Freescale KwikStik (Cortex-M4)
> > RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]
> > RedBoot>
> >
> > step2:Prepare the app from the examples directory (ELF fomart)
> > If I use the default kernel setting(the startup setting is ROM),build
> > the examples with the kernel,
> > get the hello(elf fomart).
> > then use the gdb tool download the hello
> > (gdb) set remotebaud 38400
> > (gdb) target remote /dev/ttyUSB0
> > Remote debugging using /dev/ttyUSB0
> > 0x00003aa2 in ?? ()
> > (gdb) load hello
> > Loading section .rom_vectors, size 0x8 lma 0x0
> > Load failed
> > (gdb)
> >
>
> You can't load ROM startup with RedBoot. There is an experimental FLASH
> startup
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623 that will enable
> loading applications in Flash by means of Internal Flash driver
> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001561 . With these you
> should be able to load and run application, but GDB usage is limited
> because current GDB stub doesn't support hardware breakpoints.
>
> > if I use the starup setting SRAM for the kernel,then do as above
> >
> > (gdb) set remotebaud 38400
> > (gdb) target remote /dev/ttyUSB0
> > Remote debugging using /dev/ttyUSB0
> > 0x00003aa2 in ?? ()
> > (gdb) load hello
> > Loading section .rom_vectors, size 0x8 lma 0x1fff8400
> > Loading section .ARM.exidx, size 0x10 lma 0x1fff8408
> > Loading section .text, size 0x4dbc lma 0x1fff8418
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> > Ignoring packet error, continuing...
> >
> > I want to download the app to the RAM for debug,so I think the second
> > kernel startup setting is right,
> > but I don't know somewhere else to make the change,
> > can anyone help me,where is the bug, and how to debug?
> >
>
> SRAM startup is not intended for use with Redboot but with JTAG. You can
> use OpenOCD or J-Link.
>
> I hope this helps.
>
> 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

Re: [ECOS] Re: Troubles when develop app with Kwikstik

[Ilija Kocho]

On 07.09.2012 05:29, tangwei wrote:
> Dear Ilija,
>
> you said
>
>> SRAM startup is not intended for use with Redboot but with JTAG. You can
>> use OpenOCD or J-Link.
> but I found many examples in the net,which use Redboot(ROM startup burn into the on-chip flash)to debug the RAM startup APP(elf fomat) by the gdb com connect style not JTAG.
>
> steps are same as I have mentioned below. Do you mean only the Kwikstik not support this debug style? Thanks

1. Different platforms may have different memory layout set-ups.

2. Do not confuse SRAM with RAM startup. They are not the same.
TWR-K70F120M for instance provides both RAM and SRAM startup. Check it
and see differences.

The SRAM startup (i refer to Kinetis ports) when loaded uses some SRAM
locations which are also in use by RedBoot. Theoretically it would be
possible to avoid this, but it will shrink the available SRAM. If you
are willing to play, you can try to make custom memory layout by using
sram2s memory layout which keeps one 32KiB SRAM bank free.

I hope this helps

Ilija

>
>
>
> ----------------------------------------
>> Date: Mon, 27 Aug 2012 08:52:48 +0200
>> From: ilijak@siva.com.mk
>> To: tziang@hotmail.com
>> CC: ecos-discuss@ecos.sourceware.org
>> Subject: [ECOS] Re: Troubles when develop app with Kwikstik
>>
>> On 21.08.2012 05:52, tangwei wrote:
>>> Dear all,
>>>
>>> I have a FreeScale's Kwikstik board,and have troubles when develop
>>> with it as below
>>>
>>> setp1:Use the default redboot setting for KwikStik,and then download
>>> the bin into the flash,
>>> then connect the COM,I get the below string on the computer,it seems
>>> the redboot is OK.
>>>
>>> Platform: Freescale KwikStik (Cortex-M4)
>>> RAM: 0x1fff8000-0x20007000 [0x1fffb6a8-0x20007000 available]
>>> RedBoot>
>>>
>>> step2:Prepare the app from the examples directory (ELF fomart)
>>> If I use the default kernel setting(the startup setting is ROM),build
>>> the examples with the kernel,
>>> get the hello(elf fomart).
>>> then use the gdb tool download the hello
>>> (gdb) set remotebaud 38400
>>> (gdb) target remote /dev/ttyUSB0
>>> Remote debugging using /dev/ttyUSB0
>>> 0x00003aa2 in ?? ()
>>> (gdb) load hello
>>> Loading section .rom_vectors, size 0x8 lma 0x0
>>> Load failed
>>> (gdb)
>>>
>> You can't load ROM startup with RedBoot. There is an experimental FLASH
>> startup
>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001623 that will enable
>> loading applications in Flash by means of Internal Flash driver
>> http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001561 . With these you
>> should be able to load and run application, but GDB usage is limited
>> because current GDB stub doesn't support hardware breakpoints.
>>
>>> if I use the starup setting SRAM for the kernel,then do as above
>>>
>>> (gdb) set remotebaud 38400
>>> (gdb) target remote /dev/ttyUSB0
>>> Remote debugging using /dev/ttyUSB0
>>> 0x00003aa2 in ?? ()
>>> (gdb) load hello
>>> Loading section .rom_vectors, size 0x8 lma 0x1fff8400
>>> Loading section .ARM.exidx, size 0x10 lma 0x1fff8408
>>> Loading section .text, size 0x4dbc lma 0x1fff8418
>>> Ignoring packet error, continuing...
>>> Ignoring packet error, continuing...
>>> Ignoring packet error, continuing...
>>> Ignoring packet error, continuing...
>>> Ignoring packet error, continuing...
>>>
>>> I want to download the app to the RAM for debug,so I think the second
>>> kernel startup setting is right,
>>> but I don't know somewhere else to make the change,
>>> can anyone help me,where is the bug, and how to debug?
>>>
>> SRAM startup is not intended for use with Redboot but with JTAG. You can
>> use OpenOCD or J-Link.
>>
>> I hope this helps.
>>
>> 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