-
Notifications
You must be signed in to change notification settings - Fork 10
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
No success with WiPy and new build #11
Comments
I believe that pyboard.py has an issue trying to enter the raw-repl if your boot.py script prints anything. So I guess the first thing to do would be to verify that you can use pyboard.py with your WiPy. If pyboard.py doesn't work, then rshell won't work. I should mention that in the docs. I should probably see if pyboard.py can be fixed properly. Hmm. I added support in rshell for connecting to multiple pyboards. As a consequence if you run rshell with no arguments, it will autoconnect to pyboards. I think I may have forgotten to add a connect command for telnet (should be easy to fix though). Can you try pass -p IP-address when you invoke rshell? I'll see about printing a better error message if no boards are connected. There is a boards command which lists all of the connected boards. |
I'm short of time until tomorrow when I'll test the USB and pyboard.py. This was the outcome of a brief test using telnet. I modified boot.py by commenting out all the print statements and did a reset via telnet.
So it connects if I specify the IP, but I can't get a working REPL. |
Bah - figures - I tested lots of other things and forgot repl! I also just pushed a bunch of other changes. I'll fix the repl issue today. |
ok - the repl on the wipy should work properly now. You can also connect over telnet after starting rshell by using 'connect telnet hostname' or 'connect telnet ip-address'. The boards command will show whatever boards are currently connected. If you're connected to multiple boards you can copy files from one board to the other. |
USB serial to the wipy still doesn't work (at least copying files to the wipy doesn't work). i think I have an idea how to fix it, but it will need some more investigation. |
REPL on the wipy is now fine, and file copy works in both directions. I got no joy from 'connect telnet ip-address' but I'm unclear why you'd want to do this, given the options of running the REPL or running a Telnet session direct from the terminal. For the sake of completeness this is the outcome when I try it
|
You can use the connect command to connect to multiple wipy's or pyboards at the same time. For the following example, I'll start rshell which will auto-connect to the pyboard. Then I'll use the connect telnet command to connect to the wipy, and finally copy a file from the pyboard to the wipy.
You can put a board.py file in the boards filesystem and put a line like this in it:
and then when you use the boards command it will show as that name instead of wipy or pyboard. rshell just does an import board, so board.py can be anywhere in the seach path. When you use /flash or /sd it refers to the filesystem on the first board. You can use /board-name/flash or /board-name/sd to get to an arbitrary board. repl with no arguments connects to the first board. repl board-name connects to the indicated board. Trying to connect to a Wipy while you're already connected will fail (since the wipy only supports one connection) which is what you were seeing above. |
It works well with the Pyboard but I can't connect to the WiPy either wirelessly or via the expansion board USB. My main.py is just a single line comment. boot.py is
Firstly, wired connection. Demo that hardware is OK - successive connections using Miniterm:
Now trying using rshell: evidently some connectivity is occurring, then it falls over.
alias wipy='/mnt/qnap2/python/rshell/rshell.py -p /dev/wipy'
Wireless connectivity: successive telnet sessions
Now trying rshell
The text was updated successfully, but these errors were encountered: