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 1001031] New: fis_write function in redboot not writng into flash properly - help needed Date: Wed, 08 Sep 2010 04:36:00 -0000 [thread overview] Message-ID: <bug-1001031-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=1001031 Summary: fis_write function in redboot not writng into flash properly - help needed Product: eCos Version: unknown Platform: Other (please specify) OS/Version: ARM Status: UNCONFIRMED Severity: normal Priority: normal Component: RedBoot AssignedTo: unassigned@bugs.ecos.sourceware.org ReportedBy: ravishkumar@bel.co.in QAContact: ecos-bugs@ecos.sourceware.org CC: ecos-bugs@ecos.sourceware.org Class: Advice Request Hi , We are trying to port Qnx on our custom board(based on i.Mx27). We have couple of issues while porting : Following are those issues : 1) The custom board has Spansion 64 MB flash(S29WS512P), where as the i.Mx27ADS has 32 MB flash S29WS256N We have built the redboot for our board. We are able to download the Qnx image into RAM serially by load command. Qnx runs from RAM. Problem : When we tried to flash the Qnx image using fis write command, redboot does not write into the flash properly. It writes the first two bytes repeatedly for 16 bytes. Ex : Suppose Qnx image(in RAM) is having first bytes as 0C and C0. These two bytes are repeated for next 16 bytes in flash. Again 17th and 18th bytes of RAM repeat in flash for next 16 bytes. The cycle repeats. 2) FEC : i) We run the Qnx from RAM (downloaded into RAM). ii) We are able to configure the ip address (en0) for the board. iii) The localhost ping works properly. Problem : When we ping the computer connected to the board (FEC), i) PC does not respond. But we could see the ICMP packets being sent in a network sniffer running on PC. ii) When we ping the board from PC, the board does not respond. But ICMP packets are sent by PC. iii) When we broadcast from PC, then the board responds. Please throw some light on these problems and help us to resolve the issues. Thanks, Krishna, Ravish -- 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:[~2010-09-08 4:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-09-08 4:36 bugzilla-daemon [this message] 2015-03-20 5:06 ` [Issue 1001031] " bugzilla-daemon 2015-03-20 5:11 ` bugzilla-daemon 2010-09-08 4:36 [Issue 1001031] New: " 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-1001031-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).