From: "Li Weichen" <iaadoa@gmail.com>
To: "'Kipisz, Steven'" <s-kipisz2@ti.com>, 'Olav Kongas' <ok@artecdesign.ee>
Cc: linux-omap-open-source@linux.omap.com
Subject: RE: Basic question: how to flash omap system with ccs?
Date: Mon, 28 Nov 2005 21:36:48 +0800 [thread overview]
Message-ID: <438b07fb.4ce8c5ea.624e.6224@mx.gmail.com> (raw)
In-Reply-To: <99E943D7AA8E3A448619E1F809F2A2A201160C67@dlee04.ent.ti.com>
Hi Steven,
Thank you for your reply. But I cannot find how to download a file to the
board in CCS since I am quite unfamiliar with this software. Could you
please be so kind to show me?
Thanks and best regards!
Li Weichen
2005-11-28
> -----Original Message-----
> From: Kipisz, Steven [mailto:s-kipisz2@ti.com]
> Sent: Monday, November 28, 2005 9:20 PM
> To: Olav Kongas; Li Weichen
> Cc: linux-omap-open-source@linux.omap.com
> Subject: RE: Basic question: how to flash omap system with ccs?
>
> CCS 3.1 supports ELF file formats, which is the same format as the
> u-boot executable. You should be able to use a CCS gel file to
> configure SDRAM, peripherals, etc. so that CCS can load u-boot into
> SDRAM and run it. Once u-boot is running, you download u-boot.bin and
> write it to flash. If anybody has a gel file for a 5912, he/she could
> probably send it to you. I've don't this with other OMAP platforms.
>
> The SRAM option sounds interesting. You could probably build u-boot for
> SDRAM (the normal build) and save the binary file as something like
> u-boot-sdram.bin. Then build a SRAM version - look at
> u-boot/board/omap5912osk/config.mk. The TEXT_BASE value is where u-boot
> will load. Change this to a SRAM area, rebuild u-boot, and use CCS to
> download the ELF format u-boot. Once that is running in SRAM, download
> and flash the SDRAM version .bin file. I've never tried this, but it
> sounds like it might work, assuming the binary image and the executing
> image fit into the 250k SRAM.
>
> Steve K.
>
> -----Original Message-----
> From: linux-omap-open-source-bounces@linux.omap.com
> [mailto:linux-omap-open-source-bounces@linux.omap.com] On Behalf Of Olav
> Kongas
> Sent: Sunday, November 27, 2005 3:55 PM
> To: Li Weichen
> Cc: linux-omap-open-source@linux.omap.com
> Subject: Re: Basic question: how to flash omap system with ccs?
>
>
>
> On Sun, 27 Nov 2005, Li Weichen wrote:
>
> > Hi all,
> >
> > I have an TI XDS560 emulator and CCS 3.1 by hand. Can I load the
> > bootloader, kernel and file system with them? I have never used CCS
> before,
> > so I eagerly hope someone could show me the steps or where I can find
> the
> > answer.
>
> I'm right now working on the same problem. I'm using XDS510
> if that matters. The aim is to transfer u-boot to omap5912's
> SRAM and then burn it into the virgin onboard flash of our
> custom board. I plan to transfer kernel and the rest later
> when already booted up from u-boot.
>
> Initially I started to modify u-boot so that it could run in
> SRAM, with jtag connected, so that I could use u-boot
> functionality to burn itself into flash. However, it turned
> out more and more changes to u-boot were needed so I decided
> to whip up a little custom flash programmer for that.
>
> The scheme is the following: the u-boot image will be
> appended to the flash programmer image, the result will be
> converted to the TI's COFF format and transferred from CCS
> over jtag to omap's SRAM, where the programmer will be
> started.
>
> I have CCS and jtag emulator working. I really recommend to
> carefully read the instructions at Spectrum Digital's
> webpage on how to set it all correctly up. I have written a
> little COFF header generator to convert raw images into TI's
> COFF; that's the format the CCS agrees to load over jtag. If
> you want the tool just let me know. Currently I am working
> on the flash programmer.
>
> Olav
>
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
next prev parent reply other threads:[~2005-11-28 13:36 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 13:19 Basic question: how to flash omap system with ccs? Kipisz, Steven
2005-11-28 13:36 ` Li Weichen [this message]
2005-11-28 14:09 ` is the OMAP5912 support boot by NAND flash? andy
2005-11-28 23:59 ` Kyungmin Park
2005-11-29 0:25 ` andy
2005-11-29 2:14 ` Kyungmin Park
2005-11-29 2:31 ` andy
2005-11-29 2:41 ` Kyungmin Park
2005-11-29 2:52 ` andy
2005-11-28 15:18 ` Basic question: how to flash omap system with ccs? Olav Kongas
-- strict thread matches above, loose matches on Subject: below --
2005-12-02 14:40 Hunter, Jon
[not found] <C51F43ABFC95844490F0529B60753BF402B6B8D9@dlee02.ent.ti.com>
2005-12-02 1:36 ` Li Weichen
[not found] <438dd76f.621835a8.5534.1d69@mx.gmail.com>
2005-12-01 10:55 ` Olav Kongas
2005-12-02 1:09 ` Li Weichen
2005-12-05 13:42 ` Olav Kongas
2005-12-05 13:54 ` Li Weichen
2005-11-29 15:13 Hunter, Jon
[not found] <C51F43ABFC95844490F0529B60753BF402A3AF75@dlee02.ent.ti.com>
2005-11-29 3:07 ` Li Weichen
2005-11-28 15:46 Hunter, Jon
2005-11-27 8:06 Li Weichen
2005-11-27 21:55 ` Olav Kongas
2005-11-28 12:29 ` Li Weichen
2005-11-28 15:30 ` Olav Kongas
2005-11-29 14:42 ` Olav Kongas
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=438b07fb.4ce8c5ea.624e.6224@mx.gmail.com \
--to=iaadoa@gmail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=ok@artecdesign.ee \
--cc=s-kipisz2@ti.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