@alexthefifth if you are talking to me, I haven't gotten it to boot directly from the SD card yet.

I have tried the `util recover -emmc -from sd -f firmimg.d7`but that fails with write errors. Running the mmcinfo command seems to indicate that the eMMC has failed.


So a litte update from me.

I can get into recovery mode (shorting SW2 procedure)

NOTE: After stopping u-boot in this development mode.  You may need to
      warm/cold reset the server when booting iDRAC manually as BIOS
      may have already viewed iDRAC as unresponsive.
 

 
RECOVER:Max retries occured for both N/N-1 paths, OR forced recover.
 
iDRAC7=>
 

I can also do tftpboot -f firmimg.d7

iDRAC7=> tftpboot -f firmimg.d7
reset PHY of sh_g_eth.0
1000Base/Full
Using sh_g_eth.0 device
TFTP from server 192.168.0.214; our IP address is 192.168.0.245
Filename 'firmimg.d7'.
Load address: 0x0
Loading:   60 MB
Bytes transferred = 63064294 (3c248e6 hex)
 

However, as soon as I do

go addr 0x81000000
 

It immediately tries booting and then starts polling for my flashcard instead of booting the actual firmimg.d7 image.

U-Boot 2009.08-00088-g121cddc (Nov 17 2014 - 05:50:46) Avocent (0.0.3) EVB, Build: jenkins-idrac-yocto-release-505
 
CPU: SH-4A
BOARD: R0P7757LC00xxRL (C0 step) board
BOOT: Insecure, HRK not generated
DRAM:  240MB
  (240MB of 256MB total DRAM is available on U-Boot)
ENV:   Using primary env area.
In:    serial
Out:   serial
Err:   serial
PCIe:  Bridge loaded with 0x18000 bytes
WDT2:  Booted Lower Vector, 'uboot1'
sh_mmcif: 0, sh-sdhi: 1
Net:   sh_eth.0, sh_g_eth.0
INFO: 00:002 Start-up -to- util_idrac_main()
INFO: 00:005 U-Boot 2009.08-00088-g121cddc (Nov 17 2014 - 05:50:46) Avocent (0.0.3) EVB
INFO: 00:008 U-Boot checkin date(05-10-2013) Version(1.0.183)
INFO: 00:006 iDRAC PPID <NULL>
INFO: 00:003 SPI NOR init 4096 KiB N25Q032 bus=0 cs=0, speed=1000000, mode=3
INFO: 00:007 SH-4A Product: Major Ver=0x31  Minor Ver=0x14 C4 Little endian
             Family=0x10    Major Ver=0x30  Minor Ver=0x0b
PASS: 00:015 Dedicated monolithic mgmt NIC disabled
INFO: 00:129 BCM54610 OUI=0x3fffff  Model=0x3f  Revision=0x0f PhyAddr=1
INFO: 00:006 SD CARD: is not found
INFO: 00:042 EMMC:   Device: sh_mmcif   Manufacturer ID: 90   OEM: 14a
             Name: HYNIX   Tran Speed: 25000000   Rd Block Len: 512
             MMC version 4.0   High Capacity: Yes   Capacity: 0
INFO: 00:019 CPLD: Major Ver=0x1  Minor Ver=0x0  Maint Ver=0x4
             Planar: Type=0x07  Rev=0x4  Rework=0x0  Scratch/PathRetry=0x0f
PASS: 00:014 Coin cell detected good,  AD=0x399 low water=0x2c1
PASS: 00:007 PCIe C0 Ver=0.15 MCTP en, CRC=0x8e9b6875 @0x8efbf954 cnt=0x18000
INFO: 00:007 Init PCIe mailbox(PCIe 0xFFEE0150=0x40010000)
INFO: 00:006 mode=normal
INFO: 00:003 reset_cause=recover
PASS: 00:004 Booted Lower Vector, 'uboot1' wdt2cnt=0
INFO: 00:006 wdt0cnt=0
PASS: 00:002 SMR0 no sermux env, default 0xd4
INFO: 00:004 GRACR=0x3c HISEL=0x00 SIRQCR5_D=0x03 SIRQCR6_D=0x01 LADMSK0=0xff2
             MRSTCR0=0xfedffe7f MRSTCR1=0xfff3ff0f MRSTCR2=0x7f80feff
             BARMAP=0x1 BCR=0x85000000 NCER=0x01fc NCMCR=0x0006 NCCSR=0x0303
PASS: 00:021 etherc0=C8:1F:66:C0:DE:0D
             getherc0=C8:1F:66:C0:DE:0E
INFO: 00:008 Fan logic is not modified on Non-AC power up
INFO: 00:052 Env and backup CRC'ed ok
*** no text signature found ***
INFO: 00:650 Sync eMMC/SPI NOR/Alternate u-boot images
PASS: 00:075 Current u-boot1 1.0.183 verified with 'ubootN1'
             Trailer Struct - Missing start token, exp=0xc0de1111 rec=0x701070
PASS: 03:978 Verify OS Images N-1: CRC32 OK: Kernel=0x8c86b2b Rootfs=0xb0e73b0
FAIL: 00:007 Boot device=emmc  Boot partition5/N-1
             Boot Path Retry:P1/N=3 P5/N-1=3  Recover
INFO: 00:000 05:096
 

WDT2: Disabled
 

######################################################################
** No bootable iDRAC image is found **
** (System Health & ID LED is flashing amber at ~1/2 second rate).
To Recover iDRAC via an SD card.
1)  Format SD using FAT on a Windows box or EXT3 using Linux.
2)  Copy 'firmimg.d7' to root path.
3)  Insert SD card.
4)  System Health & ID button solid amber durning recover.
5)  Both boot paths are flashed.
######################################################################
 
Polling for SD card state change \
 

Is there something I'm missing to force it to boot from memory and the firmimg.d7 that tftp grabbed? I have a feeling that if I had a good emmc chip that as soon as I did what it asks it would flash the emmc with the firmimg.d7 file. However, I was just trying to get this thing to boot with tftpboot into an actual running idrac.

I slept over this.
Am I correct in seeing that some of the information from the eMMC is copied over to SPI during boot?
This would explain why a 1.57 flashed SPI would show iDRAC8=>.
And when the material at eMMC is not as it should, the whole shebang fails.
Still, it's possibly I just have a faulty eMMC. I'd need to nuke it, to be sure. But booting up to linux will not allow me to release all partitions. DUH.
Maybe boot from SD-card? I guess I will try that today;
- using util recovery flash both SD and SPI with 1.57
- boot from SD
- mount emmc (mmcblk0) and nuke it

Apparently direct access via debug pins have been unsuccessful?
And I would need suitable hardware for it.

Well this might be the end of the road for me...I screwed up...royally and went completely backwards where I might not be able to recover.

I was trying to follow these instructions to validate I was getting a good image...

Dell R720xd iDRAC BIOS recovery (5)

However, prior to that I was messing with the `fwu dev <x>` command and I swapped to 'fwu dev 4'...which is "FLASH", which I am pretty damn sure is the 25Q03213 (U_IDRAC_SPI) chip flash memory...and NOT the CF card memory :(. This resulted in NOTHING working. The iDRAC does nothing, USB-to-UART was obviously working fine, however, after I get _nothing_. I short the pins, no output, I unplug and plug back in, nothing. Its just completely dead.

I ordered a Black CH341A programmer from Amazon. https://www.amazon.com/Organizer-EEPROM-...10089833&sr=8-3

I'm going to cross my fingers and pray that the dump from this post Dell R720xd iDRAC BIOS recovery will work on this chip (anyone else know of another U_IDRA_SPI dump), if it doesn't them I'm completely SOL and can't do anything as I didn't make a backup or anything (no way to make a backup without ordering more stuff...but now was forced to...) of the U_IDRAC_SPI chip.

Zitat von alexthefifth im Beitrag #150

---

When you boot from SD card does the system still have the issue of loud fans (for a long time) upon every restart? Or only if iDRAC loses power i.e. system gets unplugged

---

Zitat von oh2ftu im Beitrag #145

---

Alright. So I'm taking a few leaps here and there. I'm able to mount the SD-card. I can use dd, and dump something to the SD-card.util info -flashmap
How should I go forth in dumping the SPI flash? which device is it? after that, I could try reflashing it (via the same console?) with a working dump?

---

util info -flashmap"
 

From what I see of your system @oh2ftu it appears to me that there is NOTHING wrong with your SPI, and I would back it up, and leave it alone. Critical env values can be obtained easily with a uboot "printenv" command and saved off to a text file.

Zitat von kur1j im Beitrag #149

---

Yeah @ldv mentioned it here Dell R720xd iDRAC BIOS recovery (6) where you could boot directly from the SD card. Basically an alternative to the tftp option.

I want to see if I can get mine to do the above SD card boot like @ldv mentioned. If not I'll fall back to trying the tftp.

I have a hot air reworkstation and ordered the eMMC, so once it arrives I'm going to try to attempt to replace it.

To me it really doesn't make sense that the eMMC died though.

---

Zitat von oh2ftu im Beitrag #147

---

Leaving the system on will leave df and mount with hundreds of duplicate mount points.
I did manage to mount a SD-card and dump both SPI and emmc (possibly?):

1
2
3
4
5
6
7
8
 

mount /dev/mmcblk1p1 /media/card
cd /dev/
for i in mmcblk0boot*;do dd if=/dev/$i of=/media/card/$i.bin;done
for i in mmcblk0p*;do dd if=/dev/$i of=/media/card/$i.bin;done
for i in mtd*;do dd if=/dev/$i of=/media/card/$i.bin;done
umount /media/card
 
 

The last will dump the devices mtd_, mtd_ro and mtdblock_ - all seem identical.

I will have to look at the thread if someone has a pre 2.x version of the SPI-dump. What will need to be modified is at least:
- Service tag
- ethernet mac
- Licenses?

These might be located in multiple places.

I'm not sure if I've got fwu-utility, I only get the root shell of uboot.
Might just try to erase the emmc and see what that does.
The emmc seems to be 0,5 pitch, I've done TFBGA88 before without any issues. Reballing is a PITA, though a new chip would have the balls in place making it much easier.

---

Zitat von oh2ftu im Beitrag #148

---

Status report:
- Flashed v1.57 with SPI, no luck

---

Zitat

---

- Flashed original (somewhere between 2.21 and 2.40) still the same.
Using the interrupt, I can now get to iDRAC8=>
Still:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
 

iDRAC8=> fwu check 0x81000000
Checking image header CRC ... OK
Checking platform env ID..... OK
Checking kernel image CRC ... OK
Checking rootfs image CRC ... OK
Checking u-boot image CRC ... OK
Skipping u-boot update ...... NO
Checking Platform image CRC . OK
Checking processor support .. OK
Done!
iDRAC8=> fwu mmc emmc
Erasing SPI flash at 0x100000...Writing to SPI flash...done
Erasing SPI flash at 0x110000...Writing to SPI flash...done
iDRAC8=> fwu update 0x81000000
 
*** Updating Partition 1 ***
Checking image header CRC ... OK
Checking platform env ID..... OK
Checking kernel image CRC ... OK
Checking rootfs image CRC ... OK
Checking u-boot image CRC ... OK
Skipping u-boot update ...... NO
Checking Platform image CRC . OK
Checking processor support .. OK
Copying kernel image ........ mmc write failed, err=-84
*** fail to write block to device ***
Fail
[/quote]This is the same thing I get anytime I try to write to the emmc.[quote]
*** fail to update kernel image ***
*** fail to update image ***
iDRAC8=> mmcinfo
Device: sh_mmcif
Manufacturer ID: 90
OEM: 14a
Name: HYNIX
Tran Speed: 25000000
Rd Block Len: 512
MMC version 4.0
High Capacity: Yes
Capacity: 0
Bus Width: 8-bit
 

I guess it loads something from the emmc to SPI during boot, which is not ideal.

Here's what bothers me:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
 

INFO: 00:077 Env and backup CRC'ed ok
Erasing SPI flash at 0x100000...Writing to SPI flash...done
Erasing SPI flash at 0x110000...Writing to SPI flash...done
[b]*** no text signature found ***
[/b]INFO: 02:563 Sync eMMC/SPI NOR/Alternate u-boot images
[b]PASS: 00:262 Current u-boot1 1.1.31 verified with 'ubootN'
             Trailer Struct - Missing start token, exp=0xc0de1111 rec=0x0
             U-boot2 in sync with u-boot1 1.1.31[/b]
PASS: 05:803 Verify OS Images N: CRC32 OK: Kernel=0xc4135ec5 Rootfs=0x47eca7d
[b]PASS: 00:008 Boot device=emmc  Boot partition1/N
             Boot Path Retry:P1/N=0 P5/N-1=0[/b]
INFO: 00:071 No 'userexe' defined
 
 

I've ordered two blank emmc's and a few spi:s. But the SPI flashes are redundant now that I've borrowed a programmer.

---

WHAT in that last block bothers you? The "nouserexe" is normal from what I can tell., so is the no text signature which is related to ancient uboot kernels that are not in a uimage format.

Zitat von kur1j im Beitrag #153

---

Well this might be the end of the road for me...I screwed up...royally and went completely backwards where I might not be able to recover.

I was trying to follow these instructions to validate I was getting a good image...

Dell R720xd iDRAC BIOS recovery (5)

However, prior to that I was messing with the `fwu dev <x>` command and I swapped to 'fwu dev 4'...which is "FLASH", which I am pretty damn sure is the 25Q03213 (U_IDRAC_SPI) chip flash memory...and NOT the CF card memory :(. This resulted in NOTHING working. The iDRAC does nothing, USB-to-UART was obviously working fine, however, after I get _nothing_. I short the pins, no output, I unplug and plug back in, nothing. Its just completely dead.

I ordered a Black CH341A programmer from Amazon. https://www.amazon.com/Organizer-EEPROM-...10089833&sr=8-3

I'm going to cross my fingers and pray that the dump from this post Dell R720xd iDRAC BIOS recovery will work on this chip (anyone else know of another U_IDRA_SPI dump), if it doesn't them I'm completely SOL and can't do anything as I didn't make a backup or anything (no way to make a backup without ordering more stuff...but now was forced to...) of the U_IDRAC_SPI chip.

---

iDRAC7=> util info -flashmap
 
Flash Address Map EMMC:
Image    Start   End     Blk      Size in     Start       Last       Filename:
Name:    Blk:    Blk:    Cnt:     Bytes:      Address:    Address:
 
mbr      0x00000 0x00000 0x00001  0x00000200  0x00000000  0x000001ff
kernelN  0x00001 0x08001 0x08000  0x01000000  0x00000200  0x010001ff kernel.bin
rootfsN  0x08001 0x3fc01 0x37c00  0x06f80000  0x01000001  0x07f80000 rootfs.squashfs
ubootN   0x3fc01 0x40001 0x00400  0x00080000  0x06f88001  0x07008000 u-boot.bin
ext      0x40001 0x40001 0x00001  0x00000200  0x000bfc01  0x000bfe00
kernelN1 0x40002 0x48002 0x08000  0x01000000  0x00040201  0x01040200 kernel.bin
rootfsN1 0x48003 0x7fc03 0x37c00  0x06f80000  0x00048202  0x06fc8201 rootfs.squashfs
ubootN1  0x7fc04 0x80004 0x00400  0x00080000  0x0007fe03  0x000ffe02 u-boot.bin
scratch  0x80005 0x120005 0xa0000  0x14000000  0x00080204  0x14080203
pdataN   0x120006 0x122006 0x02000  0x00400000  0x00120205  0x00520204
pdataN1  0x122007 0x124007 0x02000  0x00400000  0x00122206  0x00522205
ps       0x124008 0x126008 0x02000  0x00400000  0x00124207  0x00524206
maser    0x126009 0x3e700a 0x2c1001  0x58200200  0x00126208  0x58326407
core     0x3e700b 0x3fed84 0x17d79  0x02faf200  0x003e720a  0x03396409
freshair 0x3fed8b 0x3ffd8b 0x01000  0x00200000  0x003ff985  0x005ff984
extmaser 0x401d8d 0x52dd8d 0x12c000  0x25800000  0x007fff8c  0x25ffff8b
part1    0x00001 0x40001 0x40000  0x000bfc00  0x00000200  0x000bfdff
part5    0x40002 0x80002 0x40000  0x000bfc00  0x00040201  0x000ffe00
part1_5  0x00000 0x80002 0x80002  0x10000400  0x00000000  0x100003ff
non_os   0x80005 0x3e700a 0x367005  0x6ce00a00  0x00080204  0x6ce80c03
1gig     0x00000 0x200000 0x200000  0x40000000  0x00000000  0x3fffffff
2gig     0x00000 0x400000 0x400000  0x80000000  0x00000000  0x7fffffff
3gig     0x00000 0x600000 0x600000  0xc0000000  0x00000000  0xbfffffff
 

Flash Address Map SPI NOR:
Image    Start End   Sect Size in     Start       Last       Filename:
Name:    Sect: Sect: Cnt: Bytes:      Address:    Address:
 
uboot1   000   007   008  0x00080000  0x00000000  0x0007ffff u-boot.bin
uboot2   008   015   008  0x00080000  0x00080000  0x000fffff u-boot.bin
env1     016   016   001  0x00010000  0x00100000  0x0010ffff
env2     017   017   001  0x00010000  0x00110000  0x0011ffff
fru      018   018   001  0x00010000  0x00120000  0x0012ffff fru12g.bin
res1     019   019   001  0x00010000  0x00130000  0x0013ffff
pt       020   027   008  0x00080000  0x00140000  0x001bffff
lcl      028   051   024  0x00180000  0x001c0000  0x0033ffff
res2     052   063   012  0x000c0000  0x00340000  0x003fffff
4meg     000   063   064  0x00400000  0x00000000  0x003fffff 12G_SPINOR.bin
UTIL PASS
iDRAC7=> version
 

Zitat von rgrimes im Beitrag #159

---

There is NO reason to fuss with the SPI, in all cases I have seen here the SPI is working just fine. All of these issues are centered around emmc failures.

---

Zitat von rgrimes im Beitrag #159

---

*sigh* Ok, let me put this out there, and maybe a mod can go fix that post, DO NOT, REPEAT DO NOT attempt to write firmware images to SPI, that is a BRICK that well need jtag to reprogram the SPI.

---

Zitat von rgrimes im Beitrag #159

---

I have not looked to see if we can get your system back by a dip switch that would cause it to load uboot from the emmc, there are multiple copies of uboot in a system, 2 in SPI and 2 in emmc:

---

Zitat von kur1j im Beitrag #160

---

Zitat von rgrimes im Beitrag #159

---

I have not looked to see if we can get your system back by a dip switch that would cause it to load uboot from the emmc, there are multiple copies of uboot in a system, 2 in SPI and 2 in emmc:

---

I don't think my eMMC has anything on it, it appears to be faulty, which is what brought me here in the first place, so I don't think trying to load anything from the eMMC will work.

At this point though, I was hoping I could reprogram the 25Q03213 with the Black CH341A with one of the firmware ROMs posted here. Is there something else I'm missing that I should need besides the CH341A to at least try it? At this point I don't have anything else to lose.

---

I've backed up my SPI with a CH341A. I can program it in-situ back and forth, no issues.
The EMMC seems to be very unresponsive. Maybe it just failed at the same time that I updated. I've got two chips bought on ebay, but still no shipping indication.

I'm pondering IF I should try to read the EMMC in-place, but I would need to know the how the CPU is connected to it, 1,8V or 3,3V logic - to not burn it.
Also, I'm missing a suitable SD card reader so... yea...
I'm committed to revive this board, but at what cost? I did order replacement SPI-chips, just in case.. The flashes aren't cheap either. And the whole server is ~200e shipped to my doorstep.

I've even seen the amber flashing id light but.. didn't work either. Haven't been able to boot from SD for that matter.

What SPI chip do you have? Do you have a dump of it that you would be willing to share?

From my understanding if the emmc shows 0 capacity with the mmcinfo command, then its shot.

Have you had any luck trying to boot with tftpboot?

Zitat von kur1j im Beitrag #163

---

What SPI chip do you have? Do you have a dump of it that you would be willing to share?

From my understanding if the emmc shows 0 capacity with the mmcinfo command, then its shot.

Have you had any luck trying to boot with tftpboot?

---

Zitat von kur1j im Beitrag #163

---

Have you had any luck trying to boot with tftpboot?

---