Jump to content

CryBaby

Members
  • Posts

    64
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

1169 profile views
  1. I vaguely remember having trouble with this myself. The 2mm pins were a problem too so I switched to a different board. Are you absolutely sure you have shorted the right two pins? One of those $10 USB logic analysers from eBay can be handy to see if the TX is actually TXing. They work with Pulseview from Sigrok.
  2. This will be the easiest approach, provided you have linux on your PC. If you don't then you could make another working sd card, boot your SBC with that and plug in the broken one using an adapter. Then you mount the broken card and undo whatever you did to break it. None of this is specific to a particular board.
  3. For direct connection the PC will need to run a DHCP server if you don't want to set a static IP on the SBC. You don't want two DHCP servers on your network so you will have to configure it carefully or disconnect from the router while it is running.
  4. You need to fix your network. Probably then ssh will work.
  5. It might help to use HostkeyAlgorithms +ssh-rsa in your .ssh/config stanza. Run ssh with -v for some debug output. I also have key exchange problems connecting to bullseye from newer Debian (and Windows) for which the only solution has been to use something else.
  6. Unlikely, unless the PC is ancient. Most interfaces these days have auto-MDI-X.
  7. It will probably be easiest to just set your Pi to use 192.168.137.x where x is a number between 1 and 254 that is not in use by any other device on your network. If you have more than one ethernet interface in use you may also need to set a route in your PC to use the right interface for the Pi.
  8. You'll need a route from the 192.168.137 network to the 192.168.1 network, probably in your gateway. Hopefully you have a network administrator who will cooperate.
  9. Is sshd running on your Pi? What do its logs say? Does your network have a route from 192.168.137.3 to 192.168.1.10? Can you ping it?
  10. I would guess it would usually be the same as the address but with 0 in the last place. However, you probably don't want to be messing with that at all. network-manager
  11. That's a bit inconvenient. You might be able to move the console to the external port by changing the kernel boot command. Not sure what to, maybe ttyS3 or ttyS4.
  12. Are you using minicom? Sometimes the baud rate is set to 1000000 or something really high and minicom only goes up to 150000. Try tmux or screen.
  13. It looks to me like your SPI is succeeding but the kernel then wants to use the pin for IR which is failing. So try disabling the IR. It would be easier to read text than images. Probably easier for you to post too.
×
×
  • Create New...