From: ayankumarh@gmail.com (AYAN KUMAR HALDER)
To: kernelnewbies@lists.kernelnewbies.org
Subject: ARM v7 based SoC showing random behaviour with kernel and uboot
Date: Sat, 15 Oct 2016 12:33:58 +0530 [thread overview]
Message-ID: <CAGAs2AkeVFeMhixEzEqScdRzfKWBaJWE13-o09x58AP62Ff9zQ@mail.gmail.com> (raw)
Hi,
This query is about a random behaviour observed on on 2 out of 35 ARM
v7 based chipsets. The intention here is to ask about the further
diagnostic approach that should be done to root cause the malfunction
observed only on 2 chipsets (Rest 33 chipsets are working fine
consistently). All the 35 chipsets have the same SoC architecture.
When the chipsets boot up (from uboot), I see that intermittently (1
out of 3 boots), the boot up halts/resets(sometimes) at uboot (while
accessing some registers from ddr controller) or at kernel. The
behaviour changes with temperature (some times seen prominently at
lower temperatures like -5) or with logs (adding more console logs
causes the occurence of this issue to diminish) or even by removing
some external peripheral (i2c) access during bootup or by adding
instructions like memory barriers/cache flush (which causes the
occurence of the issue to diminish).
I need some guidance/pointers to debug such issues further. Please
note that we are observing such issues on silicon (SoC) and we do not
have the fpga model available (for chipscope debugging). I need to
give a concrete explanation for the malfunction observed on the 2
chipsets.
In case if this is an inappropriate forum, I would humbly request to
let me the know the appropriate forum to ask such queries.
Regards,
Ayan Kumar Halder
reply other threads:[~2016-10-15 7:03 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=CAGAs2AkeVFeMhixEzEqScdRzfKWBaJWE13-o09x58AP62Ff9zQ@mail.gmail.com \
--to=ayankumarh@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 NNTP newsgroup(s).