Menu
What's new

what can i do when update command is not available

W

westhealth

n3wb
Joined
Oct 12, 2020
Messages
22
Reaction score
1
Location
Palm Springs, California
I am trying to update firmware on my bricked(swann dvr8-4000) device via serial.
here is the available command
firmware file is not usual digicap file and without update command, how would i go about this? thank you
firmware file




U-Boot 2010.06 (Dec 24 2012 - 19:38:50)

TI813X-GP rev 1.0

ARM clk: 1000MHz
DDR clk: 533MHz
L3 clk: 220MHz
IVA clk: 410MHz
ISS clk: 480MHz
DSS clk: 240MHz
DSP clk: 750MHz

I2C: ready
DRAM: 1 GiB
NAND: HW ECC BCH8 Selected
128 MiB
MMC: OMAP SD/MMC: 0
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ @@
@@ @@
@@ @@
@@ @@
@@ @@@ @. @. @@@@ @@ @@@@@ @@@@@@@@@ @@
@@ @@@@@ L@@ @@@ @@@@@i @@@@ @@ @@ @@ @@ @@
@@ @@ @@@. @@@ @@@ @, @@ @@ @@ @@ @@ @@
@@ @@ @@ @@@ @@@ @@;@@: @@ @@ @@ @@ @@
@@ @@ @@ @@@.l@L@ ,@@@@ @@ @@ @@ @@ @@
@@ @@ @@ l@ @@@@ @. @@ L@@ @@ @@ @@ @@ @@
@@ @@ @@ @@ @@@@ @@ C@ @@ @@ @@ @@ @@ @@
@@ @@ ,@C @@ @@@ @@ C@ @@ @@ @@ @@ @@ @@
@@ @@@@@@@ @@ @@ @@ @@@@@@ @@ @@ @@ @@ @@
@@ @@@@@ @ @ @ @@@, @@@@ @@@@@ @@ @@
@@ @@
@@ @@
@@ @@
@@ @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Net: Ethernet clocking: 0x0
Detected MACID:84:7e:40:77:56:1c
cpsw
Hit any key to stop autoboot: 0
TI813X_EVM#
TI813X_EVM#help
? - alias for 'help'
base - print or set address offset
bdinfo - print Board Info structure
boot - boot default, i.e., run 'bootcmd'
bootd - boot default, i.e., run 'bootcmd'
bootm - boot application image from memory
bootp - boot image via network using BOOTP/TFTP protocol
cmp - memory compare
colorbar- Displays a color bar using HDVPSS
coninfo - print console devices and information
cp - memory copy
crc32 - checksum calculation
dcache - enable or disable data cache
dhcp - boot image via network using DHCP/TFTP protocol
echo - echo args to console
editenv - edit environment variable
exit - exit script
false - do nothing, unsuccessfully
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls - list files in a directory (default /)
go - start application at address 'addr'
help - print command description/usage
i2c - I2C sub-system
icache - enable or disable instruction cache
iminfo - print header information for application image
imxtract- extract a part of a multi-image
itest - return true/false on integer compare
loadb - load binary file over serial line (kermit mode)
loads - load S-Record file over serial line
loady - load binary file over serial line (ymodem mode)
logo - Displays a logo using HDVPSS
loop - infinite loop on address range
md - memory display
mm - memory modify (auto-incrementing address)
mmc - MMC sub system
mmcinfo - mmcinfo <dev num>-- display MMC info
mtest - simple RAM read/write test
mw - memory write (fill)
nand - NAND sub-system
nandecc - Switch NAND ECC calculation algorithm b/w hardware and software
nboot - boot from NAND device
nfs - boot image via network using NFS protocol
nm - memory modify (constant address)
ping - send ICMP ECHO_REQUEST to network host
printenv- print environment variables
rarpboot- boot image via network using RARP/TFTP protocol
reset - Perform RESET of the CPU
run - run commands in an environment variable
saveenv - save environment variables to persistent storage
setenv - set environment variables
sf - SPI flash sub-system
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
version - print monitor version
TI813X_EVM#printenv
bootdelay=1
baudrate=115200
verify=yes
bootfile=uImage
ramdisk_file=ramdisk.gz
loadaddr=0x81000000
script_addr=0x80900000
bootargs=console=ttyO0,115200n8 noinitrd root=/dev/mtdblock4 ro rootfstype=cramfs mem=90M vram=6m earlyprintk notifyk.vpssm3_sva=0xBFFD0000 i2c_bus=3,400
bootcmd=nand read 0x81000000 0x26C0000 0x200000;logo on 0x81000000 0x81600000 0x81a00000 60 30;nand read 0x81000000 0x280000 0x300000;bootm 0x81000000
ethaddr=84:7e:40:77:56:1c
ethact=cpsw
ipaddr=192.0.0.64
serverip=192.0.0.128
stdin=serial
stdout=serial
stderr=serial

Environment size: 545/8188 bytes
 
W

westhealth

n3wb
Joined
Oct 12, 2020
Messages
22
Reaction score
1
Location
Palm Springs, California
you know when it uses digicap as a firmware file, u-boot console usually asks you if you want to update and you press U to proceed and follow the wizard to update the firmware instead of repairing what's broken.
isn't there a set of commands that will do just that instead of trying to repair what's broken?

this is what gives me if i don't stop the bootloader, thanks.

CCCCCCCC

U-Boot 2010.06 (Dec 24 2012 - 19:38:19)

TI813X-GP rev 1.0

ARM clk: 1000MHz
DDR clk: 533MHz
L3 clk: 220MHz
IVA clk: 410MHz
ISS clk: 480MHz
DSS clk: 240MHz
DSP clk: 750MHz

DRAM: 1 GiB
NAND: HW ECC BCH8 Selected
128 MiB
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI813X_EVM prompt if 2nd stage is already flashed
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x20000, size 0x40000
262144 bytes read: OK
## Starting application at 0x81000000 ...


U-Boot 2010.06 (Dec 24 2012 - 19:38:50)

TI813X-GP rev 1.0

ARM clk: 1000MHz
DDR clk: 533MHz
L3 clk: 220MHz
IVA clk: 410MHz
ISS clk: 480MHz
DSS clk: 240MHz
DSP clk: 750MHz

I2C: ready
DRAM: 1 GiB
NAND: HW ECC BCH8 Selected
128 MiB
MMC: OMAP SD/MMC: 0
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ @@
@@ @@
@@ @@
@@ @@
@@ @@@ @. @. @@@@ @@ @@@@@ @@@@@@@@@ @@
@@ @@@@@ L@@ @@@ @@@@@i @@@@ @@ @@ @@ @@ @@
@@ @@ @@@. @@@ @@@ @, @@ @@ @@ @@ @@ @@
@@ @@ @@ @@@ @@@ @@;@@: @@ @@ @@ @@ @@
@@ @@ @@ @@@.l@L@ ,@@@@ @@ @@ @@ @@ @@
@@ @@ @@ l@ @@@@ @. @@ L@@ @@ @@ @@ @@ @@
@@ @@ @@ @@ @@@@ @@ C@ @@ @@ @@ @@ @@ @@
@@ @@ ,@C @@ @@@ @@ C@ @@ @@ @@ @@ @@ @@
@@ @@@@@@@ @@ @@ @@ @@@@@@ @@ @@ @@ @@ @@
@@ @@@@@ @ @ @ @@@, @@@@ @@@@@ @@ @@
@@ @@
@@ @@
@@ @@
@@ @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Net: Ethernet clocking: 0x0
Detected MACID:84:7e:40:77:56:1c
cpsw
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x26c0000, size 0x200000
2097152 bytes read: OK
VPDMA Firmware Version = 0x4d0001ad

NAND read: device 0 offset 0x280000, size 0x300000
3145728 bytes read: OK
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2700620 Bytes = 2.6 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (zr@pub-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #10 Fri Dec 28 22:47:42 CST 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: dm385evm
vram size = 6291456 at 0x0
bootconsole [earlycon0] enabled
ti81xx_reserve: ### Reserved DDR region @85900000
reserved size = 6291456 at 0x0
FB: Reserving 6291456 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is DM385 1.0
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 21068
Kernel command line: console=ttyO0,115200n8 noinitrd root=/dev/mtdblock4 ro rootfstype=cramfs mem=90M vram=6m earlyprintk notifyk.vpssm3_sva=0xBFFD0000 i2c_bus=3,400
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 82MB 1MB = 83MB total
Memory: 78292k/78292k available, 13868k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc6000000 - 0xf8000000 ( 800 MB)
lowmem : 0xc0000000 - 0xc5a00000 ( 90 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc0042000 ( 232 kB)
.text : 0xc0042000 - 0xc051e000 (4976 kB)
.data : 0xc051e000 - 0xc056b200 ( 309 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 999.42 BogoMIPS (lpj=4997120)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
TI81XX: Map 0x85900000 to 0xfe500000 for dram barrier
TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
_omap_mux_init_gpio: Could not set gpio38
cpu_is_ti8107
clk get on i2c3 fck failed
Cannot clk_get ck_32
omap2_init_devices: LIXUEQIANG begin 8
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xc6020000
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
ti81xx_pcie: PCI scan done.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
omap2_mcspi: probe of omap2_mcspi.3 failed with error -2
omap2_mcspi: probe of omap2_mcspi.4 failed with error -2
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
tps65910 1-002d: read from reg 3f failed
tps65910 1-002d: read from reg 1e failed
set_machine_constraints: failed to enable VRTC
tps65910 1-002d: failed to register tps65910-pmic regulator
tps65910-pmic: probe of tps65910-pmic failed with error -121
tps65910 1-002d: No interrupt support, no core IRQ
omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
usb2phy: computed values rxcalib(15)DACs(42 14 14)
usb2phy: override computed values rxcalib(15)DACs(42 14 14)
usb2phy_config: musb(0) rxcalib done, rxcalib read value 6f755d76
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at c601e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
usb2phy: computed values rxcalib(15)DACs(35 14 16)
usb2phy: override computed values rxcalib(15)DACs(35 14 16)
usb2phy_config: musb(1) rxcalib done, rxcalib read value 6f71dd86
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at c6026800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
fuse init (API version 7.15)
msgmni has been set to 152
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
ahci ahci.1: forcing PORTS_IMPL to 0x1
ahci ahci.1: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.1: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi1 : ahci_platform
ata2: SATA max UDMA/133 mmio [mem 0x4a0ae000-0x4a0befff] port 0x100 irq 59
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Maf ID: 0xad, Chip ID: 0xf1 (Hynix, NAND 128MiB 3,3V 8-bit)
erasesize: 0x20000, writesize: 2048, oobsize: 64
Creating 10 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000260000 : "U-Boot-reserved"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x0000012c0000 : "File System"
0x0000012c0000-0x000001ec0000 : "Application"
0x000001ec0000-0x0000026c0000 : "Param"
0x0000026c0000-0x0000028c0000 : "logo"
0x0000028c0000-0x000008000000 : "Reserved"
0x000000000000-0x000008000000 : "Whole"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffd
usb 2-1: new high speed USB device using musb-hdrc and address 2
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
rtc-isl1208 1-006f: chip found, driver version 0.3
rtc-isl1208 1-006f: rtc core: registered rtc-isl1208 as rtc0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbffd0000
usbcore: registered new interface driver snd-usb-audio
function cs4334_modinit,line:219
function cs4334_codec_probe,line:192
Registered tvp5158 audio codec
asoc: tvp5158-hifi <-> davinci-mcasp.0 mapping ok
function cs4334_probe,line:164
function cs4334_init,line:158
asoc: cs4334 <-> davinci-mcasp.1 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
#0: TI81XX SOUND0
#1: TI81XX SOUND1
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=84:7e:40:77:56:1c
rtc-isl1208 1-006f: setting system clock to 2020-12-10 17:00:52 UTC (1607619652)
usb 2-1: New USB device found, idVendor=05e3, idProduct=0608
usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 2-1: Product: USB2.0 Hub
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 4 ports detected
ata2: SATA link down (SStatus 0 SControl 300)
ata1: SATA link down (SStatus 0 SControl 300)
cramfs_fill_nand blocks is 96
VFS: Mounted root (cramfs filesystem) readonly on device 31:4.
devtmpfs: mounted
Freeing init memory: 232K
INIT: version 2.86 booting
Please wait: booting...
Error opening /dev/fb0: No such file or directory
Starting udev
udevd (71): /proc/71/oom_adj is deprecated, please use /proc/71/oom_score_adj instead.
Remounting root file system...
Caching udev devnodes
ALSA: Restoring mixer settings...
Configuring network interfaces... PHY 0:08 not found

CPSW phy found : id is : 0x2430c54
done.
Setting up IP spoofing protection: rp_filter.
mount nfs...
INIT: Entering runlevel: 5
Starting telnet daemon.
Starting syslogd/klogd: done
usb is not ready for autoexec
cramfs_fill_nand blocks is 96
UBI: attaching mtd6 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: max. sequence number: 67
UBI: attached mtd6 to ubi0
UBI: MTD device name: "Param"
UBI: MTD device size: 8 MiB
UBI: number of good PEBs: 64
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 9
UBI: total number of reserved PEBs: 55
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 4/2
UBI: image sequence number: 1791223409
UBI: background thread "ubi_bgt0d" started, PID 742
UBI device number 0, total 64 LEBs (8257536 bytes, 7.9 MiB), available 9 LEBs (1161216 bytes, 1.1 MiB), LEB size 129024 bytes (126.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "para"
UBIFS: file system size: 5160960 bytes (5040 KiB, 4 MiB, 40 LEBs)
UBIFS: journal size: 1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 243764 bytes (238 KiB)
/etc/rc5.d/S81appinit: line 19: ./logo: not found
chmod: env.sh: Read-only file system
chmod: init.sh: Read-only file system
chmod: load.sh: Read-only file system
chmod: run.sh: Read-only file system
chmod: unload.sh: Read-only file system
chmod: validate.sh: Read-only file system
chmod: ./bin/fw_load.out: Read-only file system
chmod: ./bin/i2c_rdwr.out: Read-only file system
chmod: ./bin/mem_rdwr.out: Read-only file system
chmod: ./bin/mem_stats.out: Read-only file system
chmod: ./bin/remote_debug_client.out: Read-only file system
chmod: ./bin/sys_pri.out: Read-only file system
chmod: ./bin/vpdma_dump.out: Read-only file system
chmod: ./scripts/load_video.sh: Read-only file system
chmod: ./scripts/load_vpss.sh: Read-only file system
chmod: ./scripts/osa_kermod_load.sh: Read-only file system
chmod: ./scripts/osa_kermod_unload.sh: Read-only file system
chmod: ./scripts/send_cmd.sh: Read-only file system
chmod: ./scripts/wait_cmd.sh: Read-only file system
* Bootargs Validated for mem param *
* Bootargs Validated for notifyk.vpssm3 params *
Kernel bootargs validated
./init.sh: line 18: amixer: not found
[c6xdsp ] Remote Debug Shared Memory @ 0xbfff0000
[m3video] Remote Debug Shared Memory @ 0xbfff5020
[m3vpss ] Remote Debug Shared Memory @ 0xbfffa040
Error -3 while decompressing!
c0595b19(1919)->c517e000(4096)
Error -3 while decompressing!
c0598b19(1919)->c517e000(4096)
Error -3 while decompressing!
c0598b19(1919)->c517e000(4096)
insmod: can't read './kermod/syslink.ko': Input/output error
Setting L3 bandwidth regulator for [HDVICP0 ] to [press=[3,3] BW=2000, WM Cycles=4000]
Setting DMM priority for [DUCATI ] to [0] ( 0x4e000624 = 0x08000000 )
Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc_GateMP: No such file or directory
/dev/syslinkipc_MessageQDMA: Module install successful, device major num = 251
: No such file oDRV: Module install successful
r directory
MesDRV: Module built on Dec 24 2012 19:52:30
sageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc_Notify: No such file or directory
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
/dev/syslinkipc_HeapBufMP: No such file or directory
/dev/syslinkipc_HeapMemMP: No such file or directory
/dev/syslinkipc_ListMP: No such file or directory
/dev/syslinkipc_RingIO: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_RingIOShm: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_ClientNotifyMgr: No such file or directory
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQBufMgr: No such file or directory
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQ: No such file or directory
FrameQ driver close: : Bad file descriptor
/dev/syslinkipc_Ipc: No such file or directory
Assertion at Line no: 349 in /home/zr/DVRRDK_03.00.01.03/dvr_rdk/../ti_tools/syslink/syslink_2_10_02_17_ti810x_patched/packages/ti/syslink/utils/hlos/usr/MultiProc.c: (MultiProc_module->refCount > 0) : failed
Invalid <Core name> specified!
Usage : ./fw_load.out <startup|shutdown> <Core name> [File path]

Supported core names:
Note: [File path] argument is only required when first argument is 'startup'
OsalDrv driver open: /dev/syslinkipc_Osal: No such file or directory
OsalDrv driver close: /dev/syslinkipc_Osal: Bad file descriptor
/dev/syslinkipc_MultiProc: No such file or directory
MultiProc driver close: : Bad file descriptor
SharedRegion driver open: : No such file or directory
SharedRegion driver close: : Bad file descriptor
/dev/syslinkipc_GateMP: No such file or directory
/dev/syslinkipc_MessageQ: No such file or directory
MessageQ driver close: : Bad file descriptor
Notify driver open: /dev/syslinkipc_Notify: No such file or directory
Notify driver close: /dev/syslinkipc_Notify: Bad file descriptor
ProcMgr driver open: /dev/syslinkipc_ProcMgr: No such file or directory
ProcMgr driver close: /dev/syslinkipc_ProcMgr: Bad file descriptor
/dev/syslinkipc_HeapBufMP: No such file or directory
/dev/syslinkipc_HeapMemMP: No such file or directory
/dev/syslinkipc_ListMP: No such file or directory
/dev/syslinkipc_RingIO: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_RingIOShm: No such file or directory
RingIO driver close: : Bad file descriptor
/dev/syslinkipc_ClientNotifyMgr: No such file or directory
ClientNotifyMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQBufMgr: No such file or directory
FrameQBufMgr driver close: : Bad file descriptor
/dev/syslinkipc_FrameQ: No such file or directory
FrameQ driver close: : Bad file descriptor
/dev/syslinkipc_Ipc: No such file or directory
Assertion at Line no: 349 in /home/zr/DVRRDK_03.00.01.03/dvr_rdk/../ti_tools/syslink/syslink_2_10_02_17_ti810x_patched/packages/ti/syslink/utils/hlos/usr/MultiProc.c: (MultiProc_module->refCount > 0) : failed
Invalid <Core name> specified!
Usage : ./fw_load.out <startup|shutdown> <Core name> [File path]

Supported core names:
Note: [File path] argument is only required when first argument is 'startup'
[c6xdsp ] Remote Debug Shared Memory @ 0xbfff0000
[m3video] Remote Debug Shared Memory @ 0xbfff5020
[m3vpss ] Remote Debug Shared Memory @ 0xbfffa040
 
alastairstevenson

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,975
Reaction score
6,800
Location
Scotland
Longshot suggestion:
Put a copy of the firmware file in a blank USB stick.
Plug the USB stick in and power on the NVR.
See if that is the update method, monitoring by observing the serial console.
 
W

westhealth

n3wb
Joined
Oct 12, 2020
Messages
22
Reaction score
1
Location
Palm Springs, California
that would have been really nice, but didn't happen...
lets say I have same model working DVR and update firmware from swann OS menu on screen, if I have serial console, do i get to see the actual commands running behind the process on console?
 
W

westhealth

n3wb
Joined
Oct 12, 2020
Messages
22
Reaction score
1
Location
Palm Springs, California
it seems like most models look for files like uImage, xxx.bin or xxx.img file. is .pak file often used for firmware?
i can extract something from it like unzipping, but there is only 1 file in it that has the same name, but just without extension...
 
You must log in or register to reply here.
Top