From: reille <reille@vip.qq.com>
To: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] About bin format image output question for stm32
Date: Sun, 26 May 2013 14:33:00 -0000 [thread overview]
Message-ID: <tencent_5497057248E56198659EF177@qq.com> (raw)
Hi!
Now, I meet a strange question on stm32 platform. If i set CYGNUM_DEVS_SPI_CORTEXM_STM32_BUS1_BBUF_SIZE to 256 for stm32 spi driver, bin format image converted from elf format image is abnormal, its size become to 4KB. But i set CYGNUM_DEVS_SPI_CORTEXM_STM32_BUS1_BBUF_SIZE to 0, bin format image is normal and run OK.
By reading spi_stm32.c, i find the following code:
#if (CYGNUM_DEVS_SPI_CORTEXM_STM32_BUS1_BBUF_SIZE > 0)
static cyg_uint8 bus1_tx_bbuf [CYGNUM_DEVS_SPI_CORTEXM_STM32_BUS1_BBUF_SIZE]
__attribute__((aligned (2), section (".sram"))) = { 0 };
static cyg_uint8 bus1_rx_bbuf [CYGNUM_DEVS_SPI_CORTEXM_STM32_BUS1_BBUF_SIZE]
__attribute__((aligned (2), section (".sram"))) = { 0 };
#endif
I think that the code cause that can't convert the elf format image to bin format image normally. But why? and How to solve???
thinks!
reille
reply other threads:[~2013-05-26 14:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_5497057248E56198659EF177@qq.com \
--to=reille@vip.qq.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).