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

Reply via email to