search

raspberrypi / pytrack

17 stars 8 forks source link

Docs update #4

Closed jrobinson-uk closed 6 years ago

jrobinson-uk commented 6 years ago

I've moved the docs to a sub folder and updated all import notations

daveake commented 6 years ago

The serial port issue is that the "good uart" is used by the bluetooth module, leaving the "miniport" available on the GPIO pins. The latter has a baud rate that varies with CPU speed, and also it won't clock down to 50 baud, which is what we use if we don't need to send image data over the radio. So I've always disabled BT and mapped the good port back to the GPIO pins.

If there's a neater way of using the good port I'm all ears.

On 5 March 2018 at 15:43, XECDesign notifications@github.com wrote:

@XECDesign commented on this pull request.

In README.md https://github.com/raspberrypi/pytrack/pull/4#discussion_r172229067:

Interfacing Options --> 1-Wire --> Yes

+### Additional step for Raspberry Pi 3 +In order to use the PITs board with the Raspberry Pi 3 you will need to carry out some additional steps to disable the bluetooth (which conflicts with PITs) +

    • Edit your /boot/config.txt by typing sudo nano /boot/config.txt
    • Add dtoverlay=pi3-disable-bt to the very bottom of the file to disable bluetooth.
    • Press Ctrl + x then Enter to save and exit.
    • Finally type sudo systemctl disable hciuart followed by sudo reboot

I don't think this section is needed. If you use /dev/serial0, it should connect to the correct peripheral.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/raspberrypi/pytrack/pull/4#pullrequestreview-101210291, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBodEkoaz62ijTMquNZnamFrxmNsu1nks5tbV01gaJpZM4ScdrK .

XECDesign commented 6 years ago

raspi-config should set enable_uart=1 in config.txt, which fixes the clock issue.

If there are other issues, fair enough. I would still recommend using /dev/serial0 as it is always the peripheral that's on exposed on GPIO pins.

I don't think hciuart needs to be disabled. It should only run if you have blueooth enabled.

daveake commented 6 years ago

I've spent some time this morning setting up a Pi2 and Pi3 to check the serial port stuff.

All OK on Pi2, using ttyAMA0 or serial0.

On Pi3 though, I've only got the port working at the correct baud rate by using the dtoverlay=pi3-disable-bt line in /boot/config.txt.   Without this the radio baud rate appears to be much too high.

The "sudo systemctl disable hciuart" line not needed, as you suggested.

serial0 vs ttyAMA0 makes no difference - both work on Pi2 and both work on Pi3 with the overlay, but I'm happy to change it over to serial0 in the program if that's the recommendation.

Dave

On 06/03/2018 10:12, XECDesign wrote:

raspi-config should set enable_uart=1 in config.txt, which fixes the clock issue.

If there are other issues, fair enough. I would still recommend using /dev/serial0 as it is always the peripheral that's on exposed on GPIO pins.

I don't think hciuart needs to be disabled. It should only run if you have blueooth enabled.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/raspberrypi/pytrack/pull/4#issuecomment-370731581, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBodJPsMjjad41Riz_Bgh8eIbtSeBnUks5tbmEOgaJpZM4ScdrK.

XECDesign commented 6 years ago

Sounds good. If you actually really need ttyAMA0, then there's not much reason to change that line.