Corrupted FW - no booty

[Stan_G_]

Couple days ago I turned the Arduino edison off - I was writing a upm library and didn't need the system on.

Turned it on this evening and chaos..........

******************************

PSH KERNEL VERSION: b0182727

                WR: 20104000

******************************

SCU IPC: 0x800000d0  0xfffce92c

PSH miaHOB version: TNG.B0.VVBD.0000000c

microkernel built 23:15:13 Apr 24 2014

******* PSH loader *******

PCM page cache size = 192 KB 

Cache Constraint = 0 Pages

Arming IPC driver ..

Adding page store pool ..

PagestoreAddr(IMR Start Address) = 0x04899000

pageStoreSize(IMR Size)          = 0x00080000

*** Ready to receive application *** 

U-Boot 2014.04 (Oct 14 2014 - 15:19:04)

       Watchdog enabled

DRAM:  980.6 MiB

The above keeps cycling - once or twice it has got past this and started to load Yocto - then it dies and jumps back to the start again.

I have tried to do a FW reset (I am on a mac running OS X - latest version). Have downloaded Homebrew, run brew doctor, done the  brew install dfu-util coreutils gnu-getopt and downloaded the latest yocto image. (edison-image-ww36-14). Cd'd to the unzipped image and run ./flashall.sh

Power cycled board and held down RM and FW - but flash appeared to not find DFU device 8087:0a99 - eventually flash timed out with: Timed out while waiting for dfu device 8087:0a99 - tried power cycling board and holding down FW button but lots of nothing appeared to be happening. eventually just let go of the button (with nothing appearing to be happening and power cycled again (where it went into the boot/crash/boot cycle again. So unless I have done something really really bad it appears that 1. System cannot boot. I cannot repair FW via home-brew and cannot get system back from flash. Would really appreciate some advice at this stage. BTW - just tried the power cycle with FW pressed and eventually the system did reboot - it would appear recovery failed however because still get same syndrome of boot/reset/boot

[Stan_G_]

Just checked the device manager on my mac and on USB I can see only two devices.

MERRIFIELD - Prod 0xe005 Vendor 8086 (Intel)

FT232R USB UART Prod 6001 Vendor 0403 (FTDI)

There is no device: 0a99/vendor 8087 which it appears DFU is looking for.Just for grins I changed flashall.sh to the device/vendor of MERRIFIELD but dfu could not find it.....

[Matthias_H_Intel]

On Linux you'd have to run the script as sudo. I guess the same would apply to Mac?

[Stan_G_]

Thanks Matthias - tried as sudo but no difference. I think the big issue is that no DFU device is appearing 0a99/8087.

[Stewart_C_Intel]

Can you try adding an external 12V PSU, I saw this error in NYC, ie Merrifield only, when the autonegotiation of the USB power failed. So the Edison would power up enough with the 100mA to start booting, but then would die (and reboot), when it needed more power, eg when other parts were powered up.

Generally speaking whenever programming the flash, I ensure I have a +12V supply connected, as the power needed to burn flash is more than needed when sitting at idle, ~200mA, and I've seen enough systems fail because of slow PC's, or laptops running on batteries power saving their USB ports etc.

[Stan_G_]

Thanks for the response Stewart.

Will try that tonite - BTW both USB ports are plugged into a powered hub which is in turn plugged into a mac-mini.

[Stan_G_]

Hi - Just want to confirm power supply -  pretty sure it is OK but would rather not let the magic smoke out.

I have a 12v, tip positive 1.2A supply.

Sound OK?

Just out of a matter of interest - what is the lowest amperage required (may help someone else).

ARDUINO EDISON BTW - suspect the data may be different for other boards.

Stan

[Stewart_C_Intel]

External power is 7-15V so 12 V is fine, Sleeve is ground, tip is +ve.  Typical current for the Edison module is 200mA, but adding anything fun, eg a lot of LED's or a servo or two will quickly add a lot more power. For example a high power RGB led is 10- 20mA per channel, ie 60mA, and my favorite BlinkM MaxM can drive 2A, so it has a separate power line.

One other thing to look out for when programming flash is to ensure the mapped drive, on a Mac is /Volume/Edison is unmounted before attempting to reflash. On a Mac and some Windows, this can be automatically be remounted by the OS and that causes the reflash to fail. That's another reason I prefer to use an external supply. After issuing the "reboot ota" command I can just unplug the offending USB cable.

[Stan_G_]

Power supply worked - cannot see the flash port but /volumes/edison is there.

Operating system was still there - with external power came up fine. Now the big question is (BTW I have nothing plugged into the edison) - why did is start to now not boot unless it had some extra chunky electrons?

[Stan_G_]

Scratch that previous - can see the flash port now! - Helps if you hit refresh!

[Stan_G_]

I have found the root cause - and don't want to talk about it.

Just let it be said that a powered USB hub works best and delivers a goodly amount of power when the wall-wart power is actually connected.

On a serious note - many thanks for the advise that pinpointed the actual issue - I will now go and hide under a rock - then continue with UPM library (adafruit 16 channel servo controller!)

Stan