From: Igor Trevisan <igt1972@gmail.com>
To: barebox@lists.infradead.org
Subject: Re: IIM on iMX27 "how-to" needed
Date: Fri, 10 Feb 2012 15:13:00 +0100 [thread overview]
Message-ID: <CALQ+5afG3jjozSRaeLrt5MfmeBBgjsRh6UVHNd5RpnZ0iP7Nvg@mail.gmail.com> (raw)
In-Reply-To: <CALQ+5afyqAu7NP5yks7pJcJzbpm3u2G7USn1MSTnbby1-3r4mw@mail.gmail.com>
Sorry,
I replied to Sasha privately and not to the list!
On Fri, Feb 10, 2012 at 2:05 PM, Igor Trevisan <igt1972@gmail.com> wrote:
>>
>> You could try imx_iim0.explicit_sense_enable=0, maybe this helps.
>>
>
> Again... This helps!
> Sorry, I misunderstood the logic of the sense flag!
> (I think I owe you at least a beer...;)
>
> By the way, now I can read the first two banks:
>
> barebox:/ md -b -s /dev/imx_iim_bank1
> 00000000: 41 ce 3c ad 4d 89 93 00 00 00 00 00 00 00 00 00 A.<.M...........
> 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> barebox:/
> barebox:/
> barebox:/ md -b -s /dev/imx_iim_bank0
> 00000000: 59 20 81 40 20 00 00 00 00 00 00 00 00 00 00 00 Y .@ ...........
> 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>
> Now I would like to go further and try to program some fuse bits
> (I need to store some codes...).
> I think I need first of all to set:
> imx_iim0.permanent_write_enable=1
>
> I did this, then I tried to write with
>
> mw -b 0x10028814 0xbb
>
> but reading back I still find:
> barebox:/ md -b -s /dev/imx_iim_bank0
> 00000000: 59 20 81 40 20 00 00 00 00 00 00 00 00 00 00 00 Y .@ ...........
> 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
>
> Which is the right way to write the fuse bits?
> Thanks in advance,
> I.
>
>
>
>
> --
> "Don't find fault, find a remedy."
> (Henry Ford)
--
"Don't find fault, find a remedy."
(Henry Ford)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-02-10 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 10:36 Igor
2012-01-31 11:40 ` Sascha Hauer
2012-01-31 12:51 ` Igor Trevisan
2012-01-31 13:12 ` Sascha Hauer
[not found] ` <CALQ+5afyqAu7NP5yks7pJcJzbpm3u2G7USn1MSTnbby1-3r4mw@mail.gmail.com>
2012-02-10 14:13 ` Igor Trevisan [this message]
2012-02-10 22:59 ` Sascha Hauer
2012-02-13 9:12 ` Igor Trevisan
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=CALQ+5afG3jjozSRaeLrt5MfmeBBgjsRh6UVHNd5RpnZ0iP7Nvg@mail.gmail.com \
--to=igt1972@gmail.com \
--cc=barebox@lists.infradead.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