[Open_electroporator] seems like I got an error on line 14? missing stm_low_level.py file

John Griessen john at cibolo.com
Mon Jul 17 15:08:44 UTC 2017


On 07/16/2017 09:23 PM, Mitchell Altschuler wrote:
> I tried reloading and always got the error...

Each time you copy files, then run boot.py you get an error message from micropython?

line 14? missing stm_low_level.py file?

How about using your file manager app to view that file:
Can you get it to have non zero size?

Does it have non zero size before copying it?

Here are the file sizes I have:

john at toolbench64 [micropython_pulser_code]ll
total 56
-rw-r--r-- 1 john john   263 Apr 21 23:26 boot.py
-rw-r--r-- 1 john john    34 Apr 21 23:26 main.py
-rw-r--r-- 1 john john   962 Apr 21 23:26 nvic.py
-rw-r--r-- 1 john john  2721 Apr 21 23:26 pybcdc.inf
-rw-r--r-- 1 john john  1028 Apr 22 00:10 README.md
-rw-r--r-- 1 john john 21430 Apr 21 23:26 stm_low_level.py
-rw-r--r-- 1 john john 11641 Apr 21 23:26 tim3_enable_tim1_tim2_tim5__tim1_shuts_down.py

stm_low_level.py is the largest file.  The space available should be 128kB or 256 kB, I forgot, but either is plenty
if it is empty when you start.

Are you sure you are making the pybflash virtual drive empty before copying new files in?

You probably need more space to put that file.  Something old on pybflash needs to be deleted.
When starting micropython, but before running the commands a(xxx,xx,x) or pulse(),
you need to delete all the files in /flash or showing in a file manager called pybflash,
then copy in the above 7 files, then reset the machine by a power off/power on,
then do  pulse().
maybe you have not been giving it a reset and it still has the code as it was at first turn on.

The reset button on your box is there to use every time you want to run from what is in the files.
Otherwise, I think micropython is running from RAM after it read the files in, (before you changed them maybe).

JG


More information about the open_electroporator mailing list