Business Phone Systems

Previous Thread
Next Thread
Print Thread
Rate Thread
Joined: Apr 2018
Posts: 58
barnito Offline OP
Member
OP Offline
Member
Joined: Apr 2018
Posts: 58
I ran through the same procedure I have used before to resurrect these OS7030 we are getting sent back from from one of our customers. The install goes as expected but when booting it stops dead in its tracks. Here is the output of my terminal...

Any help would be greatly appreciated. We are a Samsung dealer and are trying to save money by repairing these in our own lab rather than sending them out to our out of warranty support vendor.

The terminal window freezes here and the MEM light stops flashing and goes solid

Code
Samsung > printenv
bootdelay=3
baudrate=38400
eth1addr=00:aa:bb:cc:dd:ff
tftpdir=.
bootfile=bt30v440.bin
mtdboot=setenv bootargs console=ttyS0,38400 root=/dev/ram0 init=/linuxrc rw initrd=0x3000000,3M rootfstype=squashfs mem=112M
updateboot=tftp 1000000 ${tftpdir}/${bootfile}; protect off 1:0-111;erase 1:0-111; cp.b ${fileaddr} 11000000 ${filesize}; protect on 1:0-111
clearenv=protect off 1:112-127;erase 1:112-127;protect on 1:112-127
nanderaseall=nand erase 0 1f300000
updatecspNAND=mw.b fffe00 ff 200200;tftp fffe00 ${tftpdir}/${cspname}; nand erase  ${scsp} 200000; nand write 1000000 ${scsp} ${filesize}
updatemspNAND=mw.b 1fffe00 ff 280200;tftp 1fffe00 ${tftpdir}/${mspname}; nand erase ${smsp}  280000; nand write 2000000 ${smsp}  ${filesize}
updateirdNAND=mw.b 2fffe00 ff 300200;tftp 2fffe00 ${tftpdir}/${irdname}; nand erase ${sird}  300000; nand write 3000000 ${sird}  ${filesize}
readcsp=nand read 1000000 ${scsp} 200000
readmsp=nand read 2000000 ${smsp} 280000
readird=nand read 3000000 ${sird} 300000
installrfs=setupgradeflag;run mtdboot; run updateirdNAND; run readird;run readmsp; loadmsp 2000000 280000; run readcsp; bootcomcerto 1000000
installvml=vmlupgradeflag;run mtdboot; run updateirdNAND; run updatecspNAND; run updatemspNAND; run readird;run readmsp;loadmsp 2000000 280000;run readcsp; bootcomcerto 1000000
install=setupgradeflag;run mtdboot; run updateirdNAND; run updatecspNAND; run updatemspNAND; run readird;run readmsp;loadmsp 2000000 280000;run readcsp; bootcomcerto 1000000
standalone=clearupgradeflag;run mtdboot; run readird;run readmsp; loadmsp 2000000 280000;run readcsp; bootcomcerto 1000000
bootcmd=run standalone
autoupgradeboot=run updateboot;run clearenv;reset
bootargs=console=ttyS0,38400 root=/dev/ram0 init=/linuxrc rw initrd=0x3000000,3M rootfstype=squashfs mem=112M
mspname=ms30v125.pkg
cspname=cs30v476.pkg
irdname=rd30v482.pkg
ipaddr=10.75.10.2
gatewayip=10.75.10.1
netmask=255.255.255.0
ethaddr=00:21:4c:99:0c:91
serverip=10.75.10.78
expip=10.0.2.12
scsp=0
smsp=400000
sird=900000
stdin=serial
stdout=serial
stderr=serial

Environment size: 2055/16380 bytes
Samsung > 
Samsung > run install
Set upgrade flag
TFTP from server 10.75.10.78; our IP address is 10.75.10.2
Filename './rd30v482.pkg'.
Load address: 0x2fffe00
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###############################################
done
Bytes transferred = 7890623 (7866bf hex)

NAND erase: device 0 offset 9437184, size 3145728 ...
nand_legacy_erase: dev_id=0x0089000f, start=9437184, len=3145728
OK

NAND write: device 0 offset 9437184, size 7890623 ...
nand_legacy_rw: dev_id=0x0089000f, start=9437184, len=7890623
 7890623 bytes written: OK
TFTP from server 10.75.10.78; our IP address is 10.75.10.2
Filename './cs30v476.pkg'.
Load address: 0xfffe00
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##############################
done
Bytes transferred = 1481384 (169aa8 hex)

NAND erase: device 0 offset 0, size 2097152 ...
nand_legacy_erase: dev_id=0x0089000f, start=0, len=2097152
OK

NAND write: device 0 offset 0, size 1481384 ...
nand_legacy_rw: dev_id=0x0089000f, start=0, len=1481384
 1481384 bytes written: OK
TFTP from server 10.75.10.78; our IP address is 10.75.10.2
Filename './ms30v125.pkg'.
Load address: 0x1fffe00
Loading: #################################################################
         #################################################################
         #################################################################
         #######################################################
done
Bytes transferred = 1279828 (138754 hex)

NAND erase: device 0 offset 4194304, size 2621440 ...
nand_legacy_erase: dev_id=0x0089000f, start=4194304, len=2621440
OK

NAND write: device 0 offset 4194304, size 1279828 ...
nand_legacy_rw: dev_id=0x0089000f, start=4194304, len=1279828
 1279828 bytes written: OK

NAND read: device 0 offset 9437184, size 3145728 ...
nand_legacy_rw: dev_id=0x0089000f, start=9437184, len=3145728
 3145728 bytes read: OK

NAND read: device 0 offset 4194304, size 2621440 ...
nand_legacy_rw: dev_id=0x0089000f, start=4194304, len=2621440
 2621440 bytes read: OK
## No elf image at address 0x02000000
## Downloading image at 02000000 ...
code_offset=0x80
code_base=500000
data_offset=135014
code_size=134f94
data_base=634f94
data_size=114
zeroinit_base=6350a8
prog_entry=100

AIFHEADER:
BL_DecompressCode=e1a00000
BL_SelfRelocCode=e1a00000
BL_DbgInitZeroInit=eb00000c
EntryPointOffset=ffb00100
ProgramExitInstr=ef000011
ImageReadOnlySize=134f94
ImageReadWriteSize=114
ImageDebugSize=2538
ImageZeroInitSize=113ac
ImageDebugType=23401
ImageBase=500000
WorkSpace=0
AddressMode=20
DataBase=0
FirstFatOffset=137660
Reserved2=0
DebugInitInstr=e1a00000
ZeroInitCode[0]=e04ec00f

NAND read: device 0 offset 0, size 2097152 ...
nand_legacy_rw: dev_id=0x0089000f, start=0, len=2097152
 2097152 bytes read: OK
MSP start address is 0x00000100
## Booting image at 01000000 ...
   Image Name:   Linux-2.6.13-rtl
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1480808 Bytes =  1.4 MB
   Load Address: 01008000
   Entry Point:  01008000
   Verifying Checksum ... OK
OK

Starting kernel ...

<start_kernel>...................................................................................
Linux version 2.6.13-rtl ([email protected]) (gcc version 3.3.2) #4 Mon Mar 10 09:58:09 KST 2014
CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
Machine: ARM-M828xx Comcerto
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists
Kernel command line: console=ttyS0,38400 root=/dev/ram0 init=/linuxrc rw initrd=0x3000000,3M rootfstype=squashfs mem=112M
PID hash table entries: 512 (order: 9, 8192 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 112MB = 112MB total
Memory: 107136KB available (2429K code, 844K data, 108K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 3072K
NET: Registered protocol family 16
Comcerto GPIO: init
Comcerto GPIO: GPIOs 0 5 6 configured as IRQ source(s)
Comcerto PCI: init
Comcerto PCI: Comcerto device is not configured in PCI host
        Verify that HBMODE_n(low) pin is high and HBBURSTEN_n(high) pin is low
        On Mindspeed MH02-D370-xxx board, remove jumper JPCISLV1
SCSI subsystem initialized
SPI core: loaded version 0.2
NetWinder Floating Point Emulator V0.97 (double precision)
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
squashfs: LZMA suppport for slax.org by jro
devfs: 2004-01-31 Richard Gooch ([email protected])
devfs: boot_options: 0x0
Initializing Cryptographic API
Crypto engine S/W registered
Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 2 ports, IRQ sharing enabled
Serial: Comcerto 16550 serial driver $Revision: 1.1.1.1 $
ttyS0 at MMIO 0x10090000 (irq = 41) is a 16550A
ttyS1 at MMIO 0x10094000 (irq = 58) is a 16550A
io scheduler noop registered
RAMDISK driver initialized: 1 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
skb pool filled with 512 skb
m828xx_msp_start()
stop EMAC0 control
stop_emac0: already stopped
m828xx_msp_ready()


Last edited by barnito; 06/05/18 09:26 PM.
Atcom VoIP Demo
VoIP Demo
Joined: Dec 2010
Posts: 679
Member
*****
Offline
Member
*****
Joined: Dec 2010
Posts: 679
What is the software version of the files you are using to recover it? It looks like you need the 4.93 software

Joined: Apr 2018
Posts: 58
barnito Offline OP
Member
OP Offline
Member
Joined: Apr 2018
Posts: 58
Where do you see that it requires 4.93? The bootloader is 440.

Joined: Apr 2018
Posts: 58
barnito Offline OP
Member
OP Offline
Member
Joined: Apr 2018
Posts: 58
Originally Posted by Biztel Cuban Okie Tech
What is the software version of the files you are using to recover it? It looks like you need the 4.93 software

4.82

Joined: Aug 2006
Posts: 1,769
Likes: 7
Moderator-Iwatsu
*****
Offline
Moderator-Iwatsu
*****
Joined: Aug 2006
Posts: 1,769
Likes: 7
Version 4.93 is the version Samsung introduced to change the file system that would stop 7030s from bricking in the first place. The whole recovery process fixes the file system problem, so it's necessary to use 4.93 software.


Sometimes the thoughts in my head get so bored, they go for a stroll through my mouth. This is rarely a good thing.
Joined: Apr 2018
Posts: 58
barnito Offline OP
Member
OP Offline
Member
Joined: Apr 2018
Posts: 58
Originally Posted by JBean3329
Version 4.93 is the version Samsung introduced to change the file system that would stop 7030s from bricking in the first place. The whole recovery process fixes the file system problem, so it's necessary to use 4.93 software.

Ok, I will give it a shot.

Joined: Apr 2018
Posts: 58
barnito Offline OP
Member
OP Offline
Member
Joined: Apr 2018
Posts: 58
Do you have a guide to do it from SIO? The one I have only outlines the steps to do it VIA OSDM.

Originally Posted by JBean3329
Version 4.93 is the version Samsung introduced to change the file system that would stop 7030s from bricking in the first place. The whole recovery process fixes the file system problem, so it's necessary to use 4.93 software.

Joined: Sep 2001
Posts: 2,290
Likes: 4
pvj Offline
Moderator-Executone-Isoetec, Samsung
*****
Offline
Moderator-Executone-Isoetec, Samsung
*****
Joined: Sep 2001
Posts: 2,290
Likes: 4
PM me your email address

Joined: Apr 2018
Posts: 58
barnito Offline OP
Member
OP Offline
Member
Joined: Apr 2018
Posts: 58
Thank you everyone, I just had to "run update" several times before it would pull the PKM files and write them successfully. No idea why, but now it is working, Thank you!

Last edited by barnito; 06/06/18 07:34 PM.

Moderated by  nameless, pvj 

Link Copied to Clipboard
Forum Statistics
Forums84
Topics93,826
Posts636,757
Members49,644
Most Online5,661
May 23rd, 2018
Popular Topics(Views)
Today's Birthdays
Chad Hoffman, frankhines, jnawrocki
Newest Members
PhoneGuy827, julesm, Helen.D, AlAl, mike hurford
49,643 Registered Users
Top Posters(30 Days)
ramo 12
pvj 11
Toner 9
dans 5
Who's Online Now
3 members (Coral Tech, justbill, Toner), 85 guests, and 21 robots.
Key: Admin, Global Mod, Mod
Contact Us | Sponsored by Atcom: Business Phone Systems | Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers.
©Copyright Sundance Communications 1998-2023
Powered by UBB.threads™ PHP Forum Software 7.7.5