From: Jochen Strohbeck <jochen@strohbeck.net>
To: newlib@sourceware.org
Subject: Re: Hard faults using sprintf() and float
Date: Mon, 27 Mar 2017 08:48:00 -0000 [thread overview]
Message-ID: <7e3fac0d-d907-4c07-37cb-6ece658360e2@strohbeck.net> (raw)
In-Reply-To: <d78f7654-e1e7-ce60-ba37-d51a04ebd248@arm.com>
>>> Looks like you have a problem with misaligned loads. Check your MPU
>>> configuration.
MPU is disabled in my application but this is also the case in FreeRTOS
demo code provided for SAME70. Must MPU be configured/enabled to avoid
the hard fault ?
> Your stack needs to be 8-byte aligned at all function boundaries. The
> compiler will maintain this invariant if start-up and interrupt code
> handle the startup and interrupt entry code (most m-class cores will do
> the latter automatically).
I'm afraid that I don't quite understand you. I am using the linker
script from the FreeRTOS demo. Nevertheless I changed all ALIGN(4) to
(8) but the hard fault still occurs. According to the map file I seems
that the function boundaries in the newlib code are not 8 byte aligned.
Do I have to recompile the newlib stuff to achieve 8 byte alignment for
functions ?
Can I check if the provided newlib library is ready for (Free)RTOS
applications ?
next prev parent reply other threads:[~2017-03-27 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 8:31 Jochen Strohbeck
2017-03-24 9:38 ` Sebastian Huber
2017-03-24 11:46 ` Jochen Strohbeck
2017-03-24 13:41 ` Richard Earnshaw (lists)
2017-03-27 8:48 ` Jochen Strohbeck [this message]
2017-04-03 13:19 ` Jochen Strohbeck
2017-04-03 18:57 ` onkel.jack
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=7e3fac0d-d907-4c07-37cb-6ece658360e2@strohbeck.net \
--to=jochen@strohbeck.net \
--cc=newlib@sourceware.org \
--cc=strohbeck@gmx.net \
/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).