Device dead VIM2


#1

Hi
Device is dead. On the last boot I noticed speckles dancing on the screen. I changed the cable, same result.
Then the ubuntu upgraded, and now it does not boot. I have no bios start, I hove nothing.
It is not recognised on the USB cable update system.
I got no boot, no video detection, no bios, no USB cable detection.

I can only think it was because I went through the airport XRAY machine with it and the VIM2 has no protection from radiation, no cover. I don’t have any other idea why it has died.

Best regards
Dean


#2

Hi Dean:
For your case, you can tried the M-Registor way to upgrade:

http://docs.khadas.com/develop/HowtoBootIntoUpgradeMode/#mregister-modemaskrom-mode

Kindly update us with more details if your problem don’t got resolved.

Good luck!


#3

Hi
I have a VIM 2, nothing like what is in the picture or the link you sent.
I tried the M-register - got nothing.
then I tried the serial connection… got a boot up which ended with…
[ 19.677503@3] [sdio_reinit] finish
[ 19.693788@5] bcmsdh_register: register client driver
[ 19.694069@5] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[ 19.694319@6] bcmsdh_sdmmc: bcmsdh_sdmmc_probe Enter
[ 19.694326@6] bus num (host idx)=2, slot num (rca)=1
[ 19.694332@6] found adapter info ‘DHD generic adapter’
[ 19.694466@6] sdioh_attach: set sd_f2_blocksize 256
[ 19.695280@7] dhdsdio_probe : no mutex held. set lock
[ 19.695546@6] F1 signature read @0x18000000=0x17294359
[ 19.702046@4] F1 signature OK, socitype:0x1 chip:0x4359 rev:0x9 pkg:0x2
[ 19.703123@4] DHD: dongle ram size is set to 917504(orig 917504) at 0x160000
[ 19.703243@4] wifi_platform_get_mac_addr
[ 19.703247@4] ======== bcm_wlan_get_mac_address ========
[ 19.703250@4] custom wifi mac is not set
[ 19.703268@4] dhd_conf_set_chiprev: chip=0x4359, chiprev=9
[ 19.703320@4] dhd_conf_set_conf_path_by_nv_path: config_path=/lib/firmware/brcm/config.txt
[ 19.704358@7] dhd_os_open_image: /lib/firmware/brcm/config.txt (184 bytes) open success
[ 19.705961@7] dhd_conf_read_nv_by_chip: nv_by_chip_count=5
[ 19.705967@7] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=0, name=nvram_ap6212.txt
[ 19.705972@7] dhd_conf_read_nv_by_chip: chip=0xa9a6, chiprev=1, name=nvram_ap6212a.txt
[ 19.705976@7] dhd_conf_read_nv_by_chip: chip=0x4345, chiprev=6, name=nvram_ap6255.txt
[ 19.705980@7] dhd_conf_read_nv_by_chip: chip=0x4354, chiprev=2, name=nvram_ap6356.txt
[ 19.705984@7] dhd_conf_read_nv_by_chip: chip=0x4359, chiprev=9, name=nvram_ap6359sa.txt
[ 19.706301@7] dhd_conf_read_config: kso_enable = 0
[ 19.712497@7] wl_create_event_handler(): thread:wl_event_handler:9f2 started
[ 19.712527@6] tsk Enter, tsk = 0xffffffc0b4ba1a90
[ 19.713458@7] dhd_attach(): thread:dhd_watchdog_thread:9f3 started
[ 19.713702@5] dhd_attach(): thread:dhd_dpc:9f4 started
[ 19.713809@5] dhd_attach(): thread:dhd_rxf:9f5 started
[ 19.713823@5] dhd_deferred_work_init: work queue initialized
[ 19.736709@4] Dongle Host Driver, version 1.363.59.144.2.git ®
[ 19.737694@4] Register interface [wlan0] MAC: ac:83:f3:d4:5d:04
[ 19.737694@4]
[ 19.737732@6] wl_event_handler: was terminated
[ 19.737759@4] wl_destroy_event_handler(): thread:wl_event_handler:9f2 terminated OK
[ 19.737768@4] dhd_wl_ioctl: returning as busstate=0
[ 19.737872@4] bcmsdh_oob_intr_unregister: Enter
[ 19.737875@4] bcmsdh_oob_intr_unregister: irq is not registered
[ 19.737888@4] dhd_txglom_enable: enable 0
[ 19.737892@4] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0
[ 19.737895@4] dhd_conf_set_txglom_params: txglom_bucket_size=0
[ 19.737899@4] dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0, bus_txglom=-1
[ 19.737902@4] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0
[ 19.737906@4] sdioh_set_mode: set txglom_mode to multi-desc
[ 19.737910@4] dhd_bus_devreset: WLAN OFF DONE
[ 19.738008@4] wifi_platform_set_power = 0
[ 19.738012@4] ======== PULL WL_REG_ON LOW! ========
[ 19.738017@4] dhdsdio_probe : the lock is released.
[ 19.738145@4] dhd_module_init: Exit err=0
[ 19.871907@4] aufs 4.9-20170703
[ 23.960705@4] CONFIG-ERROR)
Ubuntu 16.04.4 LTS Khadas ttyS0

Khadas login:


#4

Do you know what the CONFIG-ERROR is all about ?


#5

You upgraded a Ubuntu ROM on your VIM2, and from the printing log you posted, your VIM2 device still works.

Which version Ubuntu ROM you installed?