Getting started
Getting started
Hello,
I received my WiPy board with dev board today... I soldered in the headers and plugged it into USB.
My understanding is that I should have a serial port and a disk, but I only get the serial port. And I can't see anything over that serial port.
I can connect to the WiPi with my phone so Wifi works but I don't have telnet on my phone to connect to the WiPi.
Do I need to do anything special to get the disk drive? I tried both USB 3.0 normal and charging ports on my PC. I don't have WiFi on my PC so I can't connect directly to the WiPi from PC. How can I enable serial console over USB port to change WiPi into client mode or enable the disk drive to put the code into the boot file?
I've read quite a few posts on here sorry if I missed the one that explains this issue.
I received my WiPy board with dev board today... I soldered in the headers and plugged it into USB.
My understanding is that I should have a serial port and a disk, but I only get the serial port. And I can't see anything over that serial port.
I can connect to the WiPi with my phone so Wifi works but I don't have telnet on my phone to connect to the WiPi.
Do I need to do anything special to get the disk drive? I tried both USB 3.0 normal and charging ports on my PC. I don't have WiFi on my PC so I can't connect directly to the WiPi from PC. How can I enable serial console over USB port to change WiPi into client mode or enable the disk drive to put the code into the boot file?
I've read quite a few posts on here sorry if I missed the one that explains this issue.
Christian Ehlers - Pycom
- danicampora
- Posts: 342
- Joined: Tue Sep 30, 2014 7:20 am
- Contact:
Re: Getting started
Unfortunately you need a telnet connection to activate the REPL duplication on the uart. Once you are on telnet do:
If you put that in your boot.py (via the ftp server), than you will always have the serial terminal after power up.
Code: Select all
from machine import UART
import os
uart = UART(0, baudrate=115200)
os.dupterm(uart)
Re: Getting started
OK thanks... looks like I'll have to get a USB Wifi adapter first.
Christian Ehlers - Pycom
- pythoncoder
- Posts: 5956
- Joined: Fri Jul 18, 2014 8:01 am
- Location: UK
- Contact:
Re: Getting started
@danicampora Out of interest why not ship with a boot.py that enables the USB? I found it odd to see /dev/ttyUSB0 yet be unable to use it.
Peter Hinch
Index to my micropython libraries.
Index to my micropython libraries.
- danicampora
- Posts: 342
- Joined: Tue Sep 30, 2014 7:20 am
- Contact:
Re: Getting started
Could be an option. But not everyone ordered the expansion board. And those UART pins can be used for many things besides the UART, and since Telnet is the default REPL and it's easy to enable the duplication. I understand that the lack of proper docs doesn't help...
Re: Getting started
It's been a while since I got a 2nd go at my WiPy as I was buried in a lot of work.
I finally managed to get the REPL via serial, but not with the supplied devsys board. I tried the dev board both under Windows 10 (with built-in and latest FTDI drivers) as well as latest Ubuntu Linux but wouldn't get anything on the serial port. I tried both the micropython submodule from the wipy github source tree as well as the latest trunk version.
I finally decided to wire the WiPy directly to an FTDI module I knew was working and I instantly got the serial prompt. So I'm wondering if there are any special drivers needed for the devsys board or if the FTDI chip on mine simply is broken. Any help would be greatly appreciated.
I finally managed to get the REPL via serial, but not with the supplied devsys board. I tried the dev board both under Windows 10 (with built-in and latest FTDI drivers) as well as latest Ubuntu Linux but wouldn't get anything on the serial port. I tried both the micropython submodule from the wipy github source tree as well as the latest trunk version.
I finally decided to wire the WiPy directly to an FTDI module I knew was working and I instantly got the serial prompt. So I'm wondering if there are any special drivers needed for the devsys board or if the FTDI chip on mine simply is broken. Any help would be greatly appreciated.
Christian Ehlers - Pycom
- danicampora
- Posts: 342
- Joined: Tue Sep 30, 2014 7:20 am
- Contact:
Re: Getting started
Is your board missing the jumpers? Does the green LED light up on the expansion board when the USB cable is connected?
Re: Getting started
Yes it was the jumpers... I had seen the hardware guide before but somehow didn't realize you had to use them.
Now I'm trying to figure out how to use a for statement on the serial REPL prompt...
Now I'm trying to figure out how to use a for statement on the serial REPL prompt...
Christian Ehlers - Pycom
Re: Getting started
Hi, I also have no jumpers. The green LED lights up, however. Do I understand correctly that I cannot connect via USB if I don't have the jumpers?danicampora wrote:Is your board missing the jumpers? Does the green LED light up on the expansion board when the USB cable is connected?
BR, Achim.
Re: Getting started
It are the jumpers.
I have received 2 boards. One with jumpers and one without.
After changing the boot.py as instructed, the putty screen stayed blank but I found a copy of the REPL in the putty.log file.
Putting the jumpers in place solved the problem.
I have received 2 boards. One with jumpers and one without.
After changing the boot.py as instructed, the putty screen stayed blank but I found a copy of the REPL in the putty.log file.
Putting the jumpers in place solved the problem.