How to connect to a Raspberry Pi Zero W using nothing but a single micro USB cable.

[YT5HOK]

That is very useful workaround... Although I failed to do it.
I would be thankful if you take a look at my config and cmdline files... Maybe there's something different...

Code: Select all

# For more options and information see
# http://rpf.io/configtxtreadme
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
#dtparam=audio=on

# Free up some RAM
gpu_mem=16

# Enable UART
enable_uart=1

# Dissable Pi3 Bluetooth (so that UART works)
dtoverlay=pi3-miniuart-bt

#Undeclock Pi3 / Overclock Pi1
#arm_freq=900
temp_limit=75

# Increase USB Current
max_usb_current=1

# Buster Support
dtoverlay=vc4-fkms-v3d

# D2RG UART over SPI
dtoverlay=sc16is752-spi0-ce0
dtoverlay=dwc2 

Code: Select all

dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait modules-load=dwc2,g_ether quiet noswap ro

Using Pi-Star V4.1.0-RC2 and modem FW Pi-Star_RPi_V4.1.0-RC2_08-Jul-2019

73 de YT5HOK

[YT5HOK]

Thanks for quick reply!

Yes, USB connected to USB port, PWR port not used. RPi booted, but there is no new hardware found. I even did "scan for hardware changes" in device manager (windows 10, as you correctly assumed).

Changed USB port, but nothing. Changed USB cable and voila! It's working!

I take care of my stuff in general and this is first broken USB cable ever, not counting those destroyed by water (rain), for which I knew they are, before arriving at destination (on my motorcycle ).

I deliberately left whole this post, cause I was writing while doing stuff one by one, so people who read this be aware of simple things that cause problems.

Sorry to bother you...

73 de YT5HOK

[YT5HOK]

Yes, of course it's useful. Better then bother with temp AP when RPi doesn't connect/find familiar Wi-Fi.

3rd party cables are no good these days, that's why I try to keep OEM cables (received with some devices) in good condition.

Thanks again for good info!

73 de YT5HOK

[AF6VN]

Changed USB port, but nothing. Changed USB cable and voila! It's working!

Any chance that was a /charge-only/ cable. Some devices come with cables that don't have data-lines, just the voltage lines.

[YT5HOK]

Could have been... But I don't think so. No way to tell now, it's gone.

Let me ask you guys one more thing... Cause this tweak is a keeper, is there any negative effect of leaving it "as is", except maybe a small impact on memory and CPU cycles?

[YT5HOK]

Understood.

Thanks again!

73 de YT5HOK