Unsolved
1 Rookie
•
28 Posts
0
38
March 19th, 2025 17:57
N2024 switch now boots to uboot prompt.
I believe I wiped out the flash on the switch. Can anyone provide instructions to reinstall the firmware into the flash on the switch?
Thanks in advance.
No Events found!
DELL-Joey C
Moderator
Moderator
•
3.7K Posts
0
March 20th, 2025 07:48
Hi,
Can you provide us a screenshot of the current screen that you are having? Usually for uboot to reinstall firmware, you will have to use a TFTP software to transfer the firmware image into the switch. UBoot will automatically reinstall the firmware. I can't recall any command to do manual installation.
Also, I'm unsure this article can help your issue, but you can have a look: http://del.ly/612120oeMY
pasha_19
1 Rookie
1 Rookie
•
28 Posts
0
March 20th, 2025 11:20
That looks like exactly what I need. I will probably try it this weekend. I expect it to be successful.
Thanks
pasha_19
1 Rookie
1 Rookie
•
28 Posts
0
March 23rd, 2025 13:43
@DELL-Joey C
I was too optimistic about that working the following here are the observed messages and the help options.
U-Boot SPL 2012.10-00079-g20827d2 (May 22 2017 - 16:58:14)
BENCH SCREENING TEST1
=========================================
IPROC_XGPLL_CTRL_3: 0x15400000
IPROC_XGPLL_STATUS: 0x800001dc
DCO code: 29
PASS
=========================================
HWRev: 0x95 AVS: 0x0 VOUT Init: 0x64 VOUT Set: 0x64
DEV ID= 0000dc14
SKU ID = 0x0
DDR type: DDR3
MEMC 0 DDR speed = 800MHz
ddr_init2: Calling soc_ddr40_set_shmoo_dram_config
ddr_init2: Calling soc_ddr40_phy_calibrate
C01. Check Power Up Reset_Bar
C02. Config and Release PLL from reset
C03. Poll PLL Lock
C04. Calibrate ZQ (ddr40_phy_calib_zq)
C05. DDR PHY VTT On (Virtual VTT setup) DISABLE all Virtual VTT
C06. DDR40_PHY_DDR3_MISC
C07. VDL Calibration
C07.1
C07.2
C07.4
C07.4.1
C07.4.4
VDL calibration result: 0x30000003 (cal_steps = 0)
C07.4.5
C07.4.6
C07.5
C08. DDR40_PHY_DDR3_MISC : Start DDR40_PHY_RDLY_ODT....
C09. Start ddr40_phy_autoidle_on (MEM_SYS_PARAM_PHY_AUTO_IDLE) ....
C10. Wait for Phy Ready
Programming controller register
ddr_init2: Calling soc_ddr40_shmoo_ctl
Validate Shmoo parameters stored in flash ..... OK
Press Ctrl-C to run Shmoo ..... skipped
Restoring Shmoo parameters from flash ..... done
Running simple memory test ..... OK
DDR Tune Completed
Micron MT29F2G08ABAEA, 128 KiB blocks, 2 KiB pages, 16B OOB, 8-bit
NAND: chipsize 256 MiB
U-Boot 2012.10-00079-g20827d2 (May 22 2017 - 16:58:14)
DRAM: 1 GiB
WARNING: Caches not enabled
NAND: Micron MT29F2G08ABAEA, 128 KiB blocks, 2 KiB pages, 16B OOB, 8-bit
NAND: chipsize 256 MiB
In: serial
Out: serial
Err: serial
arm_clk=1000MHz, axi_clk=499MHz, apb_clk=124MHz, arm_periph_clk=500MHz
Net: Registering eth
Broadcom BCM IPROC Ethernet driver 0.1
Using GMAC0 (0x18022000)
et0: ethHw_chipAttach: Chip ID: 0xdc14; phyaddr: 0x1
serdes_reset_core pbyaddr(0x1) id2(0xf)
bcmiproc_eth-0
boot in 3 s
Creating 1 MTD partitions on "nand0":
0x000000200000-0x00000f000000 : "mtd=4"
Loading file '/image2' to addr 0x70000000 with size 15725 (0x00003d6d)...
Done
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Saving Environment to NAND...
Erasing Nand...
Erasing at 0x160000 -- 100% complete.
Writing to Nand... done
Loading file '/image1' to addr 0x70000000 with size 14618 (0x0000391a)...
Done
Wrong Image Format for bootm command
ERROR: can't get kernel image!
u-boot> ?
? - alias for 'help'
base - print or set address offset
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
chpart - change active partition
cmp - memory compare
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
dhcp - boot image via network using DHCP/TFTP protocol
echo - echo args to console
env - environment handling commands
exit - exit script
false - do nothing, unsuccessfully
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
itest - return true/false on integer compare
license - print GPL license text
loadb - load binary file over serial line (kermit mode)
loady - load binary file over serial line (ymodem mode)
loop - infinite loop on address range
md - memory display
mdc - memory display cyclic
mii - MII utility commands
mm - memory modify (auto-incrementing address)
mtdparts- define flash/nand partitions
mtest - simple RAM read/write test
mw - memory write (fill)
mwc - memory write cyclic
nand - NAND sub-system
nboot - boot from NAND device
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
showvar - print local hushshell variables
sleep - delay execution for some time
source - run script from memory
test - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true - do nothing, successfully
ubi - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
version - print monitor, compiler and linker version
u-boot>
DELL-Joey C
Moderator
Moderator
•
3.7K Posts
0
March 24th, 2025 01:15
Hi,
Can you describe the steps that you have taken, did you use the steps mentioned in the URL I gave, or you only just used TFTP to transfer the file into the switch? Did you manage to run all the commands that was stated in the article?
Have you tried XMODEM? - It is commonly used for loading images into Dell switches. Usually XMODEM steps are quite different that the article in the URL. You only need to use XMODEM software option menu to transfer the file into the switch. It is different that TFTP, which rather setting up and issue commands on the switch.
pasha_19
1 Rookie
1 Rookie
•
28 Posts
0
March 24th, 2025 07:03
I downloaded the software, setup a TFTP server on windows, I unzipped the software into the tftp directory. Connected the machine to ethernet port 1 (ethernet cable and port) on the PC with a usb serial cable to COM5 and PUTTY. I power cycled the switch and got the above messages from putty. There was no chance to enter option 2 during the boot process because the following never was displayed.
There was probably no device responding to DHCP on the system which may have been a problem I can change that.
No I have not tried xmodem, possible non specific instructions (just searched for)
https://packet-lab.com/main/images/stories/CopyingFilesWithXMODEM/copying%20files%20with%20xmodem%20-%20slides.pdf
Am I interested in the rommon mode transfer using the command probably as follows?
xmodem -c C:/TFTP-root/N2000Stdv6.6.3.17.stk
Is there a preferred faster (slow speed) and if so how do I set it?
Do I need some other xmodem approach?
Dave
(edited)
pasha_19
1 Rookie
1 Rookie
•
28 Posts
0
March 24th, 2025 07:19
I have an old windows XP service pack 3 I believe box that may have hyperterminal with what I believe is a 9 pin serial console cable instead of the USB cable if that helps.
DELL-Joey C
Moderator
Moderator
•
3.7K Posts
0
March 24th, 2025 07:56
Hi,
The console port is usually a RJ45 to RS232 console cable, which is included with the switch.
My mistake on the XMODEM software, it is actually transfer option in PUTTY. Since you have installed PUTTY, the option should be here:
(This is a picture I obtain from Google)
So use the Send option, and select the file: N2000Stdv6.7.1.26.stk to be transferred to the switch.
pasha_19
1 Rookie
1 Rookie
•
28 Posts
0
March 24th, 2025 13:05
That screen matches documentation for the program extraputty a fork of putty. Will download extraputty and try probably in the next day or so. I probably want to try this with the XP box as the cable it accepts is probably RS-232 (it has the correct ends). My USB cable (for my newer computers) I read in the extraputty writeup is probably not RS-232 and is unlikely to work.
pasha_19
1 Rookie
1 Rookie
•
28 Posts
0
March 29th, 2025 21:58
Tried Xmodem send using extraputty and hyperaccess. Extraputty ran for over 1/2 hour ending with a message transfert terminated. Hyperaccess timed out on the send operation in about 15 minutes. Neither appears to have worked and they were both attempted multiple times.
DELL-Marco B
Moderator
Moderator
•
3.8K Posts
0
March 31st, 2025 07:15
Hello
unfortunately, If the suggested steps do not work, I recommend contacting our support for a more in-depth analysis.
Thanks