public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com To: ecos-bugs@ecos.sourceware.org Subject: [Issue 1001718] New: my stm32f4_discovery redboot can't work Date: Tue, 25 Dec 2012 12:02:00 -0000 [thread overview] Message-ID: <bug-1001718-13@http.bugzilla.ecoscentric.com/> (raw) Please do not reply to this email. Use the web interface provided at: https://bugzilla.ecoscentric.com/show_bug.cgi?id=1001718 Summary: my stm32f4_discovery redboot can't work Product: eCos Version: CVS Platform: stm3240g_eval (ST STM3240G-EVAL board) OS/Version: Cortex-M Status: UNCONFIRMED Severity: critical Priority: normal Component: RedBoot AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: tziang@hotmail.com QAContact: ecos-bugs@ecos.sourceware.org CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Created an attachment (id=2009) --> (https://bugzilla.ecoscentric.com/attachment.cgi?id=2009) the ecc file I use gdb-server and onboard STLINK debug the hal_if_init() in hal_if.c file step by step, and final, it stoped in cortexm_stub.c at val = _registers[offset/sizeof(target_register_t)]; in function target_register_t get_register (regnames_t reg) { target_register_t val; int offset = reg_offset(reg); if (REGSIZE(reg) > sizeof(target_register_t) || offset == -1) return -1; val = _registers[offset/sizeof(target_register_t)]; return val; } could you please give me some advices,thanks a lot attched is the ecc file my board is http://www.st.com/internet/evalboard/product/252419.jsp -- Configure issuemail: https://bugzilla.ecoscentric.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the issue. You are on the CC list for the issue.
next reply other threads:[~2012-12-25 12:02 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-25 12:02 bugzilla-daemon [this message] -- strict thread matches above, loose matches on Subject: below -- 2012-12-25 12:02 bugzilla-daemon
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-1001718-13@http.bugzilla.ecoscentric.com/ \ --to=bugzilla-daemon@ecoscentric.com \ --cc=ecos-bugs@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: linkBe 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).