RE: [ECOS] kinetis kwikstik redboot trouble

[tangwei <tziang@hotmail.com>]

[-- 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