Jump to content

Welcome to Smart Home Forum by FIBARO

Dear Guest,

 

as you can notice parts of Smart Home Forum by FIBARO is not available for you. You have to register in order to view all content and post in our community. Don't worry! Registration is a simple free process that requires minimal information for you to sign up. Become a part of of Smart Home Forum by FIBARO by creating an account.

 

As a member you can:

  •     Start new topics and reply to others
  •     Follow topics and users to get email updates
  •     Get your own profile page and make new friends
  •     Send personal messages
  •     ... and learn a lot about our system!

 

Regards,

Smart Home Forum by FIBARO Team


  • 0

HCL stuck in U-Boot after update


AJD

Question

I initiated an update of the HCL via the App a few days ago. After that the contact was lost.
I have tried all recovery options I have found with no luck.

I opened up the HCL and discovered the AM3354 module inside.
I then found the console port (3pins: 0V, Rx and Tx. 3.3V level signals) and see that it is stuck in U-Boot:

U-Boot 2011.09-00010-g16f5006-dirty (Dec 18 2013 - 20:28:15)

I2C:   ready

DRAM:  128 MiB
WARNING: Caches not enabled
No daughter card present
Did not find a recognized configuration, assuming General purpose EVM in Profile 0 with Daughter board
NAND:  HW ECC Hamming Code selected
256 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
Error: Bad compare! failed
NAND read from offset c0000 failed -74
*** Warning - readenv() failed, using default environment

Net:   cpsw
Hit any key to stop autoboot:  0
U-Boot# help
U-Boot# printenv
U-Boot#

 

It stops in U-Boot as there are some memory failure, but it does not respond to any known command.

It reboots every 8th minute.

 

The LEDs are flashing as in recovery mode, but HCL is not visible on the net and and it does do not respond on 192.168.81.1 when PC is connected directly.

I find that a bit strange. Is U-Boot really holding the recovery web server?

 

If command interface had worked, it could maybe be possible to restore the on board flash using TFTP.

Link to comment
Share on other sites

Recommended Posts

  • 0

ow on Tera term      CCCCCCCCCC.....  in UART mode.

 

now in Tera term     FILE  --->transfer ---> xmodem ---->send ---- >  hcl_u-boot_spl_2011.09.00000.img

after install

 FILE  --->transfer ---> ymodem ---->send ---->hcl_u-boot_2011.09.00000_bootdelay.bin 

 

then it start to work

in my network settings  192.168.81.5

                                             255.255.255.0

                                             192.168.81.1

 

I can't open on browser 192.168.81.1 and nothing. I can see Lan is up -->HCL-004601 login: [  124.074371] PHY: 0:00 - Link is Up - 100/Full

 

Any ideas ?

 

CCCCCC
U-Boot SPL 2011.09-00000-g5047515 (Feb 10 2016 - 16:23:40)
Build: 1.1.0_11_5047515
Texas Instruments Revision detection unimplemented
CCxyzModem - CRC mode, 2(SOH)/221(STX)/0(CAN) packets, 4 retries
Loaded 225576 bytes


U-Boot 2011.09-00000-g5047515 (Feb 10 2016 - 16:23:40)
Build: 1.1.0_11_5047515

I2C:   ready
DRAM:  128 MiB
WARNING: Caches not enabled
No daughter card present
Did not find a recognized configuration, assuming General purpose EVM in Profile 0 with Daughter board
NAND:  HW ECC BCH8 Selected
256 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - bad CRC, using default environment

Net:   cpsw
Hit any key to stop autoboot:  0
Booting main system ...
HW ECC BCH8 Selected

Loading from nand0, offset 0x2c0000
   Image Name:   Linux-3.2.0-PSP-04.06.09
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2133472 Bytes = 2 MiB
   Load Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.2.0-PSP-04.06.09
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2133472 Bytes = 2 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 3.2.0-PSP-04.06.09 (root@bamboo-remote-server-12) (gcc version 5.2.0 (Buildroot 2015.11-git-gb6e3c6f) ) #1 Mon Jun 17 08:41:53 CEST 2019
[    0.000000] AM335X ES1.0 (sgx neon )
[    0.000000] Kernel command line: console=ttyO0,115200n8 ubi.mtd=7,2048 root=/dev/mtdblock10 noinitrd rootfstype=squashfs rootwait ro
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 125420k/125420k available, 5652k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc03d1000   (3876 kB)
[    0.000000]       .init : 0xc03d1000 - 0xc0400000   ( 188 kB)
[    0.000000]       .data : 0xc0400000 - 0xc0444380   ( 273 kB)
[    0.000000]        .bss : 0xc04443a4 - 0xc0461024   ( 116 kB)
[    0.000000] NR_IRQS:396 nr_irqs:396 396
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] Total of 128 interrupts on 1 active controller
[    0.000000] OMAP clockevent source: GPTIMER2 at 24000000 Hz
[    0.000000] OMAP clocksource: GPTIMER1 at 32768 Hz
[    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
[    0.000000] Console: colour dummy device 80x30
[    0.000213] Calibrating delay loop... 498.89 BogoMIPS (lpj=2494464)
[    0.058532] pid_max: default: 32768 minimum: 301
[    0.058715] Security Framework initialized
[    0.058776] Mount-cache hash table entries: 512
[    0.059265] CPU: Testing write buffer coherency: ok
[    0.060241] devtmpfs: initialized
[    0.081634] omap_hwmod: pruss: failed to hardreset
[    0.083099] print_constraints: dummy:
[    0.083557] NET: Registered protocol family 16
[    0.086547] OMAP GPIO hardware version 0.1
[    0.089996] omap_mux_init: Add partition: #1: core, flags: 0
[    0.092681]  omap_i2c.1: alias fck already exists
[    0.093902]  omap2_mcspi.1: alias fck already exists
[    0.094207]  omap2_mcspi.2: alias fck already exists
[    0.094573]  edma.0: alias fck already exists
[    0.094604]  edma.0: alias fck already exists
[    0.094635]  edma.0: alias fck already exists
[    0.116241] bio: create slab <bio-0> at 0
[    0.118957] SCSI subsystem initialized
[    0.121154] usbcore: registered new interface driver usbfs
[    0.121582] usbcore: registered new interface driver hub
[    0.121887] usbcore: registered new device driver usb
[    0.122253] registerd cppi-dma Intr @ IRQ 17
[    0.122283] Cppi41 Init Done Qmgr-base(c887a000) dma-base(c8878000)
[    0.122283] Cppi41 Init Done
[    0.122344] musb-ti81xx musb-ti81xx: musb0, board_mode=0x13, plat_mode=0x3
[    0.122711] musb-ti81xx musb-ti81xx: musb1, board_mode=0x13, plat_mode=0x1
[    0.138610] omap_i2c omap_i2c.1: bus 1 rev2.4.0 at 100 kHz
[    0.140563] tps65910 1-002d: could not be detected
[    0.142456] Switching to clocksource gp timer
[    0.168487] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    0.168701] musb-hdrc musb-hdrc.0: dma type: dma-cppi41
[    0.169128] MUSB0 controller's USBSS revision = 4ea20800
[    0.170318] musb-hdrc musb-hdrc.0: USB OTG mode controller at c883c000 using DMA, IRQ 18
[    0.170532] musb-hdrc musb-hdrc.1: dma type: dma-cppi41
[    0.170928] MUSB1 controller's USBSS revision = 4ea20800
[    0.171478] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[    0.171661] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[    0.171875] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.171875] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.171905] usb usb1: Product: MUSB HDRC host driver
[    0.171905] usb usb1: Manufacturer: Linux 3.2.0-PSP-04.06.09 musb-hcd
[    0.171936] usb usb1: SerialNumber: musb-hdrc.1
[    0.173339] hub 1-0:1.0: USB hub found
[    0.173370] hub 1-0:1.0: 1 port detected
[    0.174346] musb-hdrc musb-hdrc.1: USB Host mode controller at c883e800 using DMA, IRQ 19
[    0.174896] NET: Registered protocol family 2
[    0.175170] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.175567] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.175689] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.175750] TCP: Hash tables configured (established 4096 bind 4096)
[    0.175781] TCP reno registered
[    0.175811] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.175842] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.176116] NET: Registered protocol family 1
[    0.176422] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.177001] cpuidle-am33xx cpuidle-am33xx.0: failed to register driver
[    0.186096] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.186126] Registering unionfs 2.5.11 (for 3.2.2)
[    0.187011] msgmni has been set to 244
[    0.191284] alg: No test for stdrng (krng)
[    0.191375] io scheduler noop registered
[    0.191406] io scheduler deadline registered
[    0.191528] io scheduler cfq registered (default)
[    0.192810] omap_uart.0: ttyO0 at MMIO 0x44e09000 (irq = 72) is a OMAP UART0
[    0.708129] console [ttyO0] enabled
[    0.712738] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
[    0.720794] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
[    0.728790] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
[    0.736785] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
[    0.744781] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
[    0.766906] brd: module loaded
[    0.777435] loop: module loaded
[    0.780853] at24 1-0051: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.788238] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write
[    0.795562] `````````````````````````````````````
[    0.800476] `````````````````````````````````````
[    0.805419] ###`###```####```###````#````````````
[    0.810333] `#```#```#```#````#`````````#````````
[    0.815277] `#```#``#`````````#````##``###```##``
[    0.820190] `#####``#`````````#`````#```#```#``#`
[    0.825134] `#```#``#`````````#`````#```#```####`
[    0.830078] `#```#```#```#````#``#``#```#```#````
[    0.834991] ###`###```###````#####`###```##``###`
[    0.839935] `````````````````````````````````````
[    0.844879] `````````````````````````````````````
[    0.849792] ````by Fibar Group sp. z o.o.````````
[    0.854736] `````````````````````````````````````
[    0.859649] The board is a HCLite.
[    0.865020] tps65217 1-0024: TPS65217 ID 0xf version 1.2
[    0.872955] print_constraints: DCDC1: 900 <--> 1800 mV at 1800 mV
[    0.881866] print_constraints: DCDC2: 900 <--> 3300 mV at 1100 mV
[    0.890716] print_constraints: DCDC3: 900 <--> 1500 mV at 1100 mV
[    0.899536] print_constraints: LDO1: 1000 <--> 3300 mV at 1800 mV
[    0.908355] print_constraints: LDO2: 900 <--> 3300 mV at 3300 mV
[    0.917083] print_constraints: LDO3: 1800 <--> 3300 mV at 3300 mV
[    0.925933] print_constraints: LDO4: 1800 <--> 3300 mV at 3300 mV
[    0.934539] omap-gpmc omap-gpmc: GPMC revision 6.0
[    0.939575] Registering NAND on CS0
[    0.944274]  omap_i2c.3: alias fck already exists
[    0.963104] omap_i2c omap_i2c.3: bus 3 rev2.4.0 at 100 kHz
[    0.971649] hp_sw: device handler registered
[    0.976165] st: Version 20101219, fixed bufsize 32768, s/g segs 256
[    0.985382] mtdoops: mtd device (mtddev=name/number) must be supplied
[    0.992614] omap2-nand driver initializing
[    0.997314] ONFI flash detected
[    1.000732] ONFI param page 0 valid
[    1.004425] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAH4)
[    1.013122] Creating 8 MTD partitions on "omap2-nand.0":
[    1.018707] 0x000000000000-0x000000020000 : "spl_1"
[    1.026000] 0x000000020000-0x000000040000 : "spl_2"
[    1.032958] 0x000000040000-0x000000060000 : "spl_3"
[    1.039978] 0x000000060000-0x000000080000 : "spl_4"
[    1.047210] 0x000000080000-0x0000000c0000 : "u-boot"
[    1.054473] 0x0000000c0000-0x0000002c0000 : "recovery_kernel"
[    1.063232] 0x0000002c0000-0x0000007c0000 : "system_kernel"
[    1.073181] 0x0000007c0000-0x000010000000 : "ubi0"
[    1.185638] UBI: attaching mtd7 to ubi0
[    1.189666] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    1.196258] UBI: logical eraseblock size:    126976 bytes
[    1.201904] UBI: smallest flash I/O unit:    2048
[    1.206817] UBI: VID header offset:          2048 (aligned 2048)
[    1.213104] UBI: data offset:                4096
[    3.382781] UBI: max. sequence number:       781060
[    3.407287] UBI: attached mtd7 to ubi0
[    3.411224] UBI: MTD device name:            "ubi0"
[    3.416381] UBI: MTD device size:            248 MiB
[    3.421569] UBI: number of good PEBs:        1986
[    3.426483] UBI: number of bad PEBs:         0
[    3.431121] UBI: number of corrupted PEBs:   0
[    3.435791] UBI: max. allowed volumes:       128
[    3.440612] UBI: wear-leveling threshold:    4096
[    3.445526] UBI: number of internal volumes: 1
[    3.450164] UBI: number of user volumes:     5
[    3.454803] UBI: available PEBs:             0
[    3.459442] UBI: total number of reserved PEBs: 1986
[    3.464660] UBI: number of PEBs reserved for bad PEB handling: 19
[    3.471008] UBI: max/mean erase counter: 482/392
[    3.475860] UBI: image sequence number:  494961731
[    3.480926] UBI: background thread "ubi_bgt0d" started, PID 472
[    3.543182] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
[    3.549682] davinci_mdio davinci_mdio.0: detected phy mask fffffffe
[    3.557159] davinci_mdio.0: probed
[    3.560699] davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver Micrel KS8051
[    3.569244] usbcore: registered new interface driver cdc_acm
[    3.575195] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    3.583801] usbcore: registered new interface driver uas
[    3.589355] Initializing USB Mass Storage driver...
[    3.594818] usbcore: registered new interface driver usb-storage
[    3.601074] USB Mass Storage support registered.
[    3.606170] usbcore: registered new interface driver ums-usbat
[    3.612823] usbcore: registered new interface driver usbserial
[    3.618957] usbserial: USB Serial Driver core
[    3.623718] USB Serial support registered for cp210x
[    3.629180] usbcore: registered new interface driver cp210x
[    3.635040] cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
[    3.642333] USB Serial support registered for FTDI USB Serial Device
[    3.649353] usbcore: registered new interface driver ftdi_sio
[    3.655395] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver
[    3.661682] USB Serial support registered for pl2303
[    3.667175] usbcore: registered new interface driver pl2303
[    3.673004] pl2303: Prolific PL2303 USB to serial adaptor driver
[    3.680145] mousedev: PS/2 mouse device common for all mice
[    3.686401] rtc-pcf8583 3-0068: chip found, driver version 1.0
[    3.694244] rtc-pcf8583 3-0068: pcf8583_get_datetime: raw data is ctl1=00, ctl2=00, ctl3=e0, sec=d5, min=01, hr=18, mday=02, wday=02, mon=04, year=09
[    3.708892] rtc-pcf8583 3-0068: rtc core: registered rtc-pcf8583 as rtc0
[    3.716186] i2c /dev entries driver
[    3.721801] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.731323] usbcore: registered new interface driver usbhid
[    3.737182] usbhid: USB HID core driver
[    3.741790] nf_conntrack version 0.5.0 (1959 buckets, 7836 max)
[    3.748504] ip_tables: (C) 2000-2006 Netfilter Core Team
[    3.754241] TCP cubic registered
[    3.757629] NET: Registered protocol family 17
[    3.762298] Registering the dns_resolver key type
[    3.767333] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.775360] ThumbEE CPU extension supported.
[    3.779907] mux: Failed to setup hwmod io irq -22
[    3.785614] Power Management for AM33XX family
[    3.794677] clock: disabling unused clocks to save power
[    3.802825] Detected MACID=bc:6a:29:d5:7a:50
[    3.808654] cpsw: Detected MACID = bc:6a:29:d5:7a:51
[    3.815856] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    3.825439] rtc-pcf8583 3-0068: pcf8583_get_datetime: raw data is ctl1=00, ctl2=00, ctl3=e0, sec=d6, min=01, hr=18, mday=02, wday=02, mon=04, year=09
[    3.839477] rtc-pcf8583 3-0068: setting system clock to 2009-04-02 18:01:56 UTC (1238695316)
[    3.855285] VFS: Mounted root (squashfs filesystem) readonly on device 31:10.
[    3.867492] devtmpfs: mounted
[    3.871124] Freeing init memory: 188K
can't run '/usr/sbin/fsck': No such file or directory
[    4.597808] UBIFS: recovery needed
[    4.864715] UBIFS: recovery completed
[    4.868682] UBIFS: mounted UBI device 0, volume 3, name "download"
[    4.875183] UBIFS: file system size:   45965312 bytes (44888 KiB, 43 MiB, 362 LEBs)
[    4.883178] UBIFS: journal size:       2285568 bytes (2232 KiB, 2 MiB, 18 LEBs)
[    4.890838] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    4.896942] UBIFS: default compressor: lzo
[    4.901214] UBIFS: reserved for root:  2171054 bytes (2120 KiB)
[    4.981933] UBIFS: recovery needed
[    5.293945] UBIFS: recovery completed
[    5.297912] UBIFS: mounted UBI device 0, volume 4, name "user_data"
[    5.304473] UBIFS: file system size:   157577216 bytes (153884 KiB, 150 MiB, 1241 LEBs)
[    5.312835] UBIFS: journal size:       7872512 bytes (7688 KiB, 7 MiB, 62 LEBs)
[    5.320495] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    5.326599] UBIFS: default compressor: lzo
[    5.330871] UBIFS: reserved for root:  4952683 bytes (4836 KiB)
Starting rsyslog daemon: OK
Starting mdev...
fibaro.scripts.S20gpiod: Starting gpiod: OK

fibaro.scripts.S20modules: Starting Modules (Fibaro STM): OK

read-only file system detected...done
fibaro.scripts.S25initialize-user-data: Initializing userd data...

fibaro.scripts.S25initialize-user-data: /usr/bin/coreutils: failed to create symbolic link '/mnt/user_data/localtime': File exists

Starting network:
[    8.054931] net eth0: CPSW phy found : id is : 0x221556
udhcpc (v1.24.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
Writing Z-Wave flash memory...
Z-Wave flash memory write failed.
Starting network plug daemon: /etc/netplug.d/netplug eth0 probe -> pid 717

Starting system message bus: done
Starting dropbear sshd: OK
Starting lighttpd: OK
Starting nginx...
fibaro.scripts.S51ntp: Starting ntpd: OK

Clearing boot flag: argc: 4
setting led 5 255
fibaro.scripts.S90fibaro-start: Starting Fibaro services...

fibaro.scripts.S90fibaro-start: Updating serial number and HW key in database...

fibaro.scripts.S90fibaro-start: Frequency: unknown

fibaro.scripts.S90fibaro-start: Starting: DbUpdater

fibaro.scripts.S90fibaro-start: Starting: HCServer

fibaro.scripts.S90fibaro-start: Starting: Zwave

fibaro.scripts.S90fibaro-start: Starting: FibaroFinderServer

fibaro.scripts.S90fibaro-start: Starting: FibaroCron

fibaro.scripts.S90fibaro-start: not available through ModulesClient

fibaro.scripts.S90fibaro-start: /opt/fibaro/scripts/checkInternet.sh: line 4: avahi-autoipd: not found

fibaro.scripts.S98remote-access: No Internet connection, restarting RA may fail

fibaro.scripts.S98remote-access: RemoteAccess - error while starting


Welcome to the new HCLITE-buildroot [HCLBR]!
HCL-004601 login: [  124.074371] PHY: 0:00 - Link is Up - 100/Full

 

 

 

 

 

 

Link to comment
Share on other sites

  • 0

I can't login serial

 

CL-004601 login: admin
Password:
Login incorrect
 

or need disconnect UART, disconnect pins, R9 and just power off/on  LAN cable?

 

 

Edited by Dasis
Link to comment
Share on other sites

  • 0
1 minute ago, Dasis said:

I flash your firmware 

 

Please login or register to see this attachment.

this is just a bootloader

check this:

 

 

Link to comment
Share on other sites

  • 0
27 minutes ago, jack.daniels said:

this is just a bootloader

check this:

 

 

 

Little bit don't understand.

 

Need do this:

 

ow on Tera term      CCCCCCCCCC.....  in UART mode.

 

now in Tera term     FILE  --->transfer ---> xmodem ---->send ---- >  hcl_cr_v10.img

after install

 FILE  --->transfer ---> ymodem ---->send ---->hcl_u-boot_2011.09.00000_bootdelay.bin

 

 

 

 

Link to comment
Share on other sites

  • 0

In Windows network seting

192.168.81.5

                                             255.255.255.0

                                             192.168.81.1

Link to comment
Share on other sites

  • 0
12 hours ago, Dasis said:

Little bit don't understand.

 

Need do this:

 

ow on Tera term

This is the board boot. If u hold the recovery button - it will boot recovery

Then you can flash 4.520 for example (with exploited security hole) and using the root exploit - flash custom recovery

When you have custom recovery (its also has root:hc2 serial/ssh login), its possible to flash custom firmware

Link to comment
Share on other sites

  • 0

Jack.daniels

How can I instal boot loader? My dont start. I Can run via Uart buy after unplug power my fibaro no start. 

I have also broken recovery . That's is really problem because I cant reset password to instal custom recovery . Do you have SD card system? Then I Can run From SD instead NAND

 

 

 

after connections power I only have black screen.  only connecting the left side of the resistor R9 causes the appearance of CCCCC.

 

 after loading your files, I come to the login 192.168.81.1 but do not accept my password.  disconnecting the power means that I have to upload files again.

 

 by pressing the plus button and uploading your files it starts running recovery but not quite.  My logs on the previous page From recovery

Edited by polon18
Link to comment
Share on other sites

  • 0

When I did it 

ow on Tera term      CCCCCCCCCC.....  in UART mode.

 

now in Tera term     FILE  --->transfer ---> xmodem ---->send ---- >  hcl_cr_v10.img

after install

 FILE  --->transfer ---> ymodem ---->send ---->hcl_u-boot_2011.09.00000_bootdelay.bin

 

System boot(you can see my log on UART), I plug Lan cable and set IP, but can't connect 192.168.81.1. Scan IP and nothing.

 

Try recovery mode (

Please login or register to see this link.

) nothing. I can't upload custom firmware. 

 

How after UART file upload and system URAT boot can find IP and upload custom firmware?

Link to comment
Share on other sites

  • 0

How can I instal boot loadera to nand and reinstal recovery?

Edited by polon18
Link to comment
Share on other sites

  • 0
10 hours ago, polon18 said:

How can I instal boot loadera to nand and reinstal recovery?

1. Connect HCL to default place (HCL was worked)

2. ow on Tera term      CCCCCCCCCC.....  in UART mode. now in Tera term     FILE>transfer-> xmodem >send >  hcl_u-boot_spl_2011.09.00000.img

after install

 FILE->transfer-> ymodem ->send->hcl_u-boot_2011.09.00000_bootdelay.bin

3. IT is boot, on UART you can see IP. On browser enter IP.

 

I can see this 

 

 

Please login or register to see this image.

/monthly_2020_10/image.png.d051c847bdc75bf064505885803fdecf.png" />

 

 

 

Try  script hcl_4140_root.py

 

get error 

 

=============== RESTART: C:\Users\user\Desktop\hcl_4140_root.py ===============
Traceback (most recent call last):
  File "C:\Users\user\Desktop\hcl_4140_root.py", line 2, in <module>
    import requests
ModuleNotFoundError: No module named 'requests'

 

Where is error?

 

 

 

Edited by Dasis
Link to comment
Share on other sites

  • 0

Hi!

 

My recovery root is damaged and by playing with the u-boot I managed to erase the recovery kernel too. Now I am left only with the normal kernel and the normal root. Although the device boots in normal mode ok, I cannot boot into recovery at all.

 

Can one of you please help me with a nand image of the recovery kernel that I can flash via u-boot? And ideally (but there is little hope with this one) the recovery root image?

 

Thanks!

Link to comment
Share on other sites

  • 0

Hi, 

On 11/21/2020 at 11:23 PM, polon18 said:

how clean kernel with u-boot?

its easy, just nand erase <offset> <size> 
offset and size depends on which kernel u need to clear (system or recovery)

 

On 11/21/2020 at 11:23 PM, polon18 said:

How I can flash custom recovery?

Not possible so far. The rootfs partition is a UBI device. ANd this version of u-boot has no UBI support. May be someone can build one.

Another problem is the boot watchdog. We have only a few minutes before system reboot itself (and 115200 speed is very slow to send 3Mb rootfs image fast enough)

Link to comment
Share on other sites

  • 0

 

I`m trying to recover  a HCL with this procedure and i have had some success 

 

- First soldered the bridges need

- Then booted into programmer mode by connecting the left side of R9 to the metal of the RJ45 plug

- File Transfer Xmodem Send hcl_u-boot_spl_2011.09.00000
- File Transfer Ymodem Send hcl_u-boot_2011.09.00000_bootdelay.bin

- Push the button to boot into recovery mode

- Send the above files again
- The unit got an ip from my DHCP server and i could reach the recovery portal
- Then recovered using a file 

Please login or register to see this link.

- And again using 

Please login or register to see this link.

0/patch.tar.gz

- Then again booted the recovery portal and performed a Recover System and need to send the X/Y transfers again

- Then logged in to the system and update to 4600

- But when rebooting in need to sens X/Y transfers again

 

It looks like i`m havind a working system, but it is not booting when applying power, in need to go to programmer mode and send the files for it to boot. 

 

Which step did i mis to repair the system so it wil boot normally, it is possible that a dead battery on the board is giving al these issues?

 

 

 

 
 

 

Edited by raymonvdm
  • Like 1
Link to comment
Share on other sites

  • 0

Добрый день. Тут кто-то говорит на русском?

Hi all, Is anybody here who speaks Russian?

 

I have the same problem with HCL.

1. soldered the bridges need - is it necessary

2. Where is the lsft side of r9 - is it necessary to make this step

3. i connect through uart to HCL and terminal shows the same picture, but a cant transfer files...

 

Maybe there are instructions for dummies  like me :-)

Please login or register to see this attachment.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...