Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with building and connecting to board #1

Open
masagava opened this issue Dec 7, 2017 · 1 comment
Open

Problem with building and connecting to board #1

masagava opened this issue Dec 7, 2017 · 1 comment

Comments

@masagava
Copy link

masagava commented Dec 7, 2017

Hi
I have some problems with using the project.
First, cmd ". ../setenv" doesnt work, and I cant understand why, and then the project is built incorrectly, so there's no chance to start ./vhcibridge. So I'm using "python vhcibridge.py" instead.
Second problem is to connect to board. It is an error "'device reports readiness to read but returned no data '
SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)"

In your code you're using a variable named 'serdev' and the path is:
"serdev = '/dev/serial/by-id/usb-FTDI_UMFT234XD_FTWJO0MJ-if00-port0
serdev = 'spy://%s?file=serial.log' % serdev"
where FTDI is USB to UART bridge and the second string is your local server(?). When I'm using only /dev/serial/..., hence the second problem.

Please help me understand what I'm doing wrong.

@dsiganos
Copy link
Owner

dsiganos commented Dec 7, 2017

This project is not meant to be a ready tool to be used by someone who is not able to do some programming/hacking and read source code. It is not finished in that way. It is at the proof of concept stage. This project may not be for you.

Here are the answers to your questions.

This is what my setenv file has:

PATH=$HOME/esp32/toolchain/default/bin:$PATH
export IDF_PATH=$HOME/esp32/esp-idf
export ESPPORT=/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_0001-if00-port0

The construct "spy://serial?file=serial.log" spies on the serial port communications and creates a log file named serial.log. It's use is optional.

The string "/dev/serial/by-id/usb-FTDI_UMFT234XD_FTWJO0MJ-if00-port0" identifies an extra serial device I am using, connected to pins: 17, 16, 5, 18. See uart.c file for more details.
This string will mean nothing to you. You need to use the name of your device.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants