dev/ttyAMA0 not showing

codm / cc2652-raspberry-pi-module

ZigBee CC2652P Raspberry Pi Module

38 stars 5 forks source link

dev/ttyAMA0 not showing #2

Closed xiki808 closed 3 years ago

xiki808 commented 3 years ago

Hi! I'm quite new to these type of configurations, and I'm sure I'm missing something.

I am running Debian 11 on my raspberry pi downloaded from here: https://raspi.debian.net/tested-images/

I have SSH access to my pi, I created config.txt in /boot directory with the following contents:

dtoverlay=miniuart-bt
enable_uart=1

When I restart my pi I cannot find /dev/ttyAMA0.

Also what should be the header configuration? Should I just take that off?

Thank you!

codmpm commented 3 years ago

Hey xiki,

what Pi do you use? The UART can be called differenlty on different models. See https://www.raspberrypi.org/documentation/computers/configuration.html#configuring-uarts

What do you mean by header configuration?

Best, Patrik

xiki808 commented 3 years ago

Thank you for your reply, I'm using Pi 4. (Raspberry Pi 4 Model B Rev 1.4r)

Also thanks for the link! .. But I'm still at a loss :/

With the header configuration I meant the 2x05 header, as mentioned in the readme, under JTAG. Is this only needed, and thus plugged on the chip only when a firmware update is needed? At the moment I have it removed.

codmpm commented 3 years ago

You mostly won't need to do anything with the JTAG headers.

Here's the config from my test-Pi (Pi4):

/boot/config.txt

enable_uart=1
dtoverlay=disable-bt

/boot/cmdline.txt

dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=80bd3ba5-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Please check if you have the settings accordingly. Of course don't copy any UUID or something. Just adjust your settings to match.

After that /dev/ttyAMA0 should be visible. Maybe check raspi-config and enable UART there.

codmpm commented 3 years ago

Oh... you should not have to "create" a config.txt - it should be already there. Be sure to edit the files in /boot/ with sudo.

xiki808 commented 3 years ago

I am in the right directory, I'm afraid the clash can be due to running Debian 11 rather than Rasbian. Even cmdline.txt is missing in my case. I'll try out what you sent.

xiki808 commented 3 years ago

This is what I currently have, not sure but maybe you can spot something weird..

codmpm commented 3 years ago

Try /dev/ttyS0- but no guaranty. I did not do anything with debian on the Pi, yet. Maybe you can use raspbian to see if eversthing works otherwise.

Also you could check where the Pi UARTs reside on a debian installation.

xiki808 commented 3 years ago

Switched to rasbian and it worked with no probs