From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11746] stm32f469 didn't work correctly......
Date: Mon, 19 Aug 2019 07:14:21 +0000 [thread overview]
Message-ID: <bug-11746-163-r3AHDrRwFf@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11746-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11746
Christophe Priouzeau <christophe.priouzeau@st.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #3 from Christophe Priouzeau <christophe.priouzeau@st.com> ---
The issue are due to a bad assembler generation by binutils tools with thumb
code on kernel.
There is two way to solver it:
1. use an old binutils tools 2.28 (see commit
b3dddb0a787352bb836ce972e4f07b59d79068e7 package/binutils: default to 2.28 for
Cortex-M targets)
2. use a more recent kernel which generate a correct assembler.
I will try to provide a new kernel configuration.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-19 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 10:06 [Buildroot] [Bug 11746] New: stm32f469 didn't work correctly bugzilla at busybox.net
2019-08-15 13:22 ` [Buildroot] [Bug 11746] " bugzilla at busybox.net
2019-08-17 13:00 ` bugzilla at busybox.net
2019-08-17 13:01 ` bugzilla at busybox.net
2019-08-17 20:55 ` bugzilla at busybox.net
2019-08-19 7:14 ` bugzilla at busybox.net [this message]
2019-09-03 12:56 ` bugzilla at busybox.net
2024-06-15 14:49 ` bugzilla
2024-06-15 14:49 ` bugzilla
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=bug-11746-163-r3AHDrRwFf@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.