Can't connect to my board with rshell, File Size Issues with pyboard.py

Discussion about programs, libraries and tools that work with MicroPython. Mostly these are provided by a third party.
Target audience: All users and developers of MicroPython.
walecka
Posts: 16
Joined: Wed Apr 08, 2020 9:50 pm

Re: Can't connect to my board with rshell, File Size Issues with pyboard.py

Post by walecka » Fri May 22, 2020 7:53 pm

update: I believe that I have found a similar issue raised in the following posts:

viewtopic.php?f=12&t=6744

https://github.com/thonny/thonny/issues/936

I am working on deciphering the solution now

Edit: User aivarannamaa suggests
flushing the target file after each written block
Any idea what exactly he means by that?

User avatar
dhylands
Posts: 3393
Joined: Mon Jan 06, 2014 6:08 pm
Location: Peachland, BC, Canada
Contact:

Re: Can't connect to my board with rshell, File Size Issues with pyboard.py

Post by dhylands » Sat May 23, 2020 2:59 am

The ip address thing is just due to the way rshell allows connecting over telnet to a WiPy and allows a hostname to be passed in.

The second exception is the real exception, which is the same as the one on the pyboard. Basically its waiting for data from the board.

kr-g
Posts: 21
Joined: Sun Dec 01, 2019 7:52 pm
Contact:

Re: Can't connect to my board with rshell, File Size Issues with pyboard.py

Post by kr-g » Tue May 26, 2020 11:44 am

walecka wrote:
Fri May 22, 2020 7:53 pm
update: I believe that I have found a similar issue raised in the following posts:

viewtopic.php?f=12&t=6744

https://github.com/thonny/thonny/issues/936

I am working on deciphering the solution now

Edit: User aivarannamaa suggests
flushing the target file after each written block
Any idea what exactly he means by that?
i also had the 250 byte limitation problem.
with my tool https://github.com/kr-g/mpycntrl

walecka
Posts: 16
Joined: Wed Apr 08, 2020 9:50 pm

Re: Can't connect to my board with rshell, File Size Issues with pyboard.py

Post by walecka » Tue Jun 02, 2020 5:09 am

In case anyone using the B-L475E-IOT01A stumbles upon this thread in the future, I fixed my issue by plugging into the other usb connector on the board, bypassing the st-link entirely. rshell is now fully functional! I had never considered this as an option, likely because I always use an st-link to program stm32 boards (programming in C, that is) so that I can make use of the debugger.

Post Reply