WiPy 3.0 getting started issues

[Xykon]

@artiom You should at least see some messages over serial (115200bps, 8n1) when pressing the reset button on the WiPy3, otherwise the serial connection isn't working properly. To put the module into firmware update mode, you also need to connect a jumper wire between P2 and GND. In that case the module should show some messages and Waiting for download on the serial port after pressing the reset button.

If you see those messages then the firmware update tool should work.

[seb]

Hi,

If you havn't updated your WiPy 3.0 firmware before trying to use it, please do this. This is a know issue with the version of the firmware the device shipped with and it should work correctly once updated.

if you don't have a one of our base boards you will need to connect RX, TX and ground to your USB UART adapter. You then need to tie P2 (fourth pin down on the left hand side) to ground and reset the board by pressing the button. When P2 is tied low during boot the device goes into bootloader mode. You should then be able to use our firmware upgrade tool to update your module. If you want to use the REPL then do not tie P2 low and connect to the UART at 115200 baud.

[Artiom]

Well I found a trick to start the upgrade. After connecting serial to USB I have to reset WiPy and after that serial console works. I upgraded the firmware.
This solved only part of the issues.

• I found that in Pymakr there is also "Project Configuration". I have to put new device address there rather than to global configuration. Still it doesn't connect. I only see a message : "Connecting on /dev/ttyUSB0". At the same time picocom works well on the same port (of cause picocom is disconnected when I try Pymakr). No REPL prompt, Download does nothing, no errors.

• boot.py is still not executed at boot. If I run it manually it still works as before.

• My test script still not turning green light on. Even tried directly through the console:

execfile("test.py")
Done

Heartbeat stops but still no green light.

[seb]

If you are using linux just double check the user running atom has the correct permissions for the serial port. Sometimes atom does fail to connect properly, once you see atom say connected, try starting the board, making sure to remove the wire connecting P2 to ground so that the device boots into normal mode.

Just to trouble shoot a bit more can you try changing the LED colour in main.py rather than boot.py to see if this makes any difference? Also try uploading via FTP and see if that works. These will help us narrow down what might be causing your issue.

[Artiom]

Some more progress in this story.

After added led code to boot.py and main.py (with different colors) it appears that boot.py suddenly works. WiPy connects to my network on boot. A have not changed anything in my config. Still using Atom. Uploaded files via WiPy's access point using Pymakr. The only thing is that picocom was connected while I was doing all those manipulations.
Now I can connect to it using my subnet's address.

Remaining points:

• Pymakr still cannot connect on ttyUSB0. I am using linux and have the right permission, because picocom run under the same user works.

• Led code from main or boot only turns off hearbeat but doesn't turn on the led.

[Xykon]

@artiom Can you please post (or send via PM) the following additional details:

• echo $USER
• cat /etc/group |grep dialout
• ls -l /dev/ttyUSB*

Directly after plugging in the serial device:

• dmesg | tail -15

[Artiom]

This post is deleted!

[Artiom]

Well. Pymakr aside, what is wrong with my code so the led is not turned on when I run it as a script?
I mean even if I put the code into main or boot the result is the same. Hearbeat is off, but no led is on.

[Xykon]

@artiom That's a timing issue. I suggest you adapt your code as follows:

import pycom,time
pycom.heartbeat(False)
time.sleep(.1)
pycom.rgbled(0x00ff00)
print("Done")

[Artiom]

Thank you. Everything works now. I hope that pymakr will be fixed as well.