Ticket #1568 (in_testing defect)

Opened 6 years ago

Last modified 6 years ago

Log in U-Boot through NOR Flash not working

Reported by: gen Owned by: openmoko-devel
Priority: normal Milestone:
Component: unknown Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible:

Description

I have tried the instructions for the NOR U-Boot at:
http://wiki.openmoko.org/wiki/U-Boot_Test_Cases#Test_Case_.238
http://wiki.openmoko.org/wiki/Getting_Started_with_your_Neo_FreeRunner
and a description someone gave on IRC: "hold in aux, then hold in power while still holding in aux until it boots"
Nothing happens when I try this.

The AUX button works okay in other contexts.
I can get to the NAND menu and boot the device up, too.

On IRC I got the impression that only some devices (or people) have this problem.

Change History

comment:1 follow-up: ↓ 2 Changed 6 years ago by werner

Could you please
gzip </dev/mtd0 >nor.gz
and either attach the file to this bug report or mail it to
werner@… ?

Thanks !

  • Werner

comment:2 in reply to: ↑ 1 Changed 6 years ago by gen

root@om-gta02:~# hexdump /dev/mtd0
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0200000

Not kidding.

comment:3 Changed 6 years ago by werner

  • Status changed from new to in_testing

Argh. I was afraid it would look like that :-(

This could be either a defective NOR chip or the programming at the
factory didn't happen for some reason.

You mentioned in private mail that you'll soon have the opportunity
to reflash the NOR. Can you please report if this was successful ?

Let's hope it's "only" a production process issue ...

comment:4 Changed 6 years ago by gen

Reflashing the NOR using a v3 debug board worked. As far as this device is concerned, the problem appears to be solved.

comment:5 Changed 6 years ago by werner

An update: we found a flaw in the production testing process that can let
devices with an incorrect NOR content pass. Don't know yet what caused the
NOR to be incorrect in the first place, though.

comment:6 Changed 6 years ago by regina_kim

gen ~! please check this ticket.

Note: See TracTickets for help on using tickets.