Windows/Linux never see board

[uf_firmware2003]

When I plug my board in it never appears in the Windows Device Manager. I have tried connecting the board to a Mint Linux machine, expecting to see ttyUSB in /dev/ but there are no new /dev/tty entries when I plug the board in. I've also checked dmesg but don't see any additional messages when I grep dmesg with the following.

dmesg | grep usb
dmesg | grep tty


When I clip on to RX0 & TX0 I do see the board boot, but it looks like the bootloader might be missing. I get 'flash read err, 1000'

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
flash read err, 1000
ets_main.c 371
ets Jun 8 2016 00:22:57

rst:0x10 (RTCWDT_RTC_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0x00
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0008,len:8
load:0x3fff0010,len:3480
load:0x40078000,len:7804
ho 0 tail 12 room 4
load:0x40080000,len:252
entry 0x40080034
I (47) boot: ESP-IDF v2.0-3-gbef9896 2nd stage bootloader
I (47) boot: compile time 05:59:45
I (47) boot: Enabling RNG early entropy source...
I (66) boot: SPI Speed : 40MHz
I (78) boot: SPI Mode : DIO
I (91) boot: SPI Flash Size : 4MB
I (103) boot: Partition Table:
I (114) boot: ## Label Usage Type ST Offset Length
I (137) boot: 0 phy_init RF data 01 01 0000f000 00001000
I (160) boot: 1 otadata OTA data 01 00 00010000 00002000
I (184) boot: 2 nvs WiFi data 01 02 00012000 0000e000
I (207) boot: 3 at_customize unknown 40 00 00020000 000e0000
I (230) boot: 4 ota_0 OTA app 00 10 00100000 00180000
I (253) boot: 5 ota_1 OTA app 00 11 00280000 00180000
I (277) boot: End of partition table
I (290) boot: Disabling RNG early entropy source...
I (307) boot: Loading app partition at offset 00100000
I (1482) boot: segment 0: paddr=0x00100018 vaddr=0x00000000 size=0x0ffe8 ( 65512)
I (1483) boot: segment 1: paddr=0x00110008 vaddr=0x3f400010 size=0x1c5f0 (116208) map
I (1499) boot: segment 2: paddr=0x0012c600 vaddr=0x3ffb0000 size=0x0215c ( 8540) load
I (1530) boot: segment 3: paddr=0x0012e764 vaddr=0x40080000 size=0x00400 ( 1024) load
I (1553) boot: segment 4: paddr=0x0012eb6c vaddr=0x40080400 size=0x1b028 (110632) load
I (1632) boot: segment 5: paddr=0x00149b9c vaddr=0x400c0000 size=0x00034 ( 52) load
I (1633) boot: segment 6: paddr=0x00149bd8 vaddr=0x00000000 size=0x06430 ( 25648)
I (1649) boot: segment 7: paddr=0x00150010 vaddr=0x400d0018 size=0x7a56c (501100) map
I (1677) heap_alloc_caps: Initializing. RAM available for dynamic allocation:
I (1699) heap_alloc_caps: At 3FFBA6B8 len 00025948 (150 KiB): DRAM
I (1720) heap_alloc_caps: At 3FFE8000 len 00018000 (96 KiB): D/IRAM
I (1742) heap_alloc_caps: At 4009B428 len 00004BD8 (18 KiB): IRAM
I (1762) cpu_start: Pro cpu up.
I (1774) cpu_start: Single core mode
I (1787) cpu_start: Pro cpu start user code
I (1848) cpu_start: Starting scheduler on PRO CPU.
I (2087) uart: queue free spaces: 10
Bin version:0.10.0

I (2089) wifi: wifi firmware version: c604573
I (2089) wifi: config NVS flash: enabled
I (2090) wifi: config nano formating: disabled
I (2098) wifi: Init dynamic tx buffer num: 32
I (2099) wifi: wifi driver task: 3ffc4eac, prio:23, stack:3584
I (2104) wifi: Init static rx buffer num: 10
I (2108) wifi: Init dynamic rx buffer num: 0
I (2112) wifi: Init rx ampdu len mblock:7
I (2116) wifi: Init lldesc rx ampdu entry mblock:4
I (2120) wifi: wifi power manager task: 0x3ffca254 prio: 21 stack: 2560
I (2127) wifi: wifi timer task: 3ffcb2d4, prio:22, stack:3584
E (2132) phy_init: PHY data partition validated
I (2154) phy: phy_version: 329, Feb 22 2017, 15:58:07, 0, 0
I (2155) wifi: mode : softAP (30:ae:a4:23:3c:fd)
I (2158) wifi: mode : sta (30:ae:a4:23:3c:fc) + softAP (30:ae:a4:23:3c:fd)
I (2161) wifi: mode : softAP (30:ae:a4:23:3c:fd)

I know my USB to Serial adapter is at COM9, ttyS8. I've tried to flash in the 'hello_world' over both RX/TX0 & RX/TX2 and I get the same error both times

$ make flash
Flashing binaries to serial port /dev/ttyS8 (app at offset 0x10000)...
esptool.py v2.3.1
Traceback (most recent call last):
File "C:/Users/LiszewJM/esp/esp-idf/components/esptool_py/esptool/esptool.py", line 2637, in <module>
_main()
File "C:/Users/LiszewJM/esp/esp-idf/components/esptool_py/esptool/esptool.py", line 2630, in _main
main()
File "C:/Users/LiszewJM/esp/esp-idf/components/esptool_py/esptool/esptool.py", line 2355, in main
esp = chip_class(args.port, initial_baud, args.trace)
File "C:/Users/LiszewJM/esp/esp-idf/components/esptool_py/esptool/esptool.py", line 193, in __init__
self._port = serial.serial_for_url(port)
File "C:/msys32/mingw32/lib/python2.7/site-packages/serial/__init__.py", line 88, in serial_for_url
instance.open()
File "C:/msys32/mingw32/lib/python2.7/site-packages/serial/serialwin32.py", line 62, in open
raise SerialException("could not open port {!r}: {!r}".format(self.portstr, ctypes.WinError()))
serial.serialutil.SerialException: could not open port '/??/COM9': WindowsError(3, 'The system cannot find the path specified.')
make: *** [/c/Users/LiszewJM/esp/esp-idf/components/esptool_py/Makefile.projbuild:55: flash] Error 1

Did I just get a bad development board? Any help would be appreciated.

[ESP_Angus]

Did I just get a bad development board? Any help would be appreciated.

Sounds like it, if there's nothing in dmesg or Windows Device Manager but the board is otherwise powered on. The only other possibility is a bad USB cable.

[chegewara]

I agree, it looks like USB cable, but could you try with ESP flash download tool on windows? Also try with different usb port.