Losing the REPL when an IRQ is triggered

[jgmdavies]

Thanks Robert - that's great.

Four differences here:

• - Couple of lines inserted in boot.py to start wifi in Station mode unless a digital input is held low.
  - Telnet terminal access with wipy in Station mode.
  - WiPy powered from PC over USB cable.
  - Unmodified build.

Jim

[Roberthh]

Still counting at 8860. We could try to make the set-up as similar as possible:

- Load today's build, which is wipy-20160913-v1.8.4-10-g081c064.zip (latest)
- No modifications to boot.py and main.py. That would require that you run in AP mode (if possible)
- Telnet access

I have no expansion board, so I cannot use USB supply. I have connected WiPy directly to the bench power supply (5V/3A).

Update: count at 35592 this morning

[jgmdavies]

I'm not having much luck.

I loaded the latest build, wipy-20160912-v1.8.4-10-g081c064, as the one you mention isn't visible at http://micropython.org/download/#wipy. I tried this version in AP mode but the timer/irq test still doesn't work here.

I tried to change my boot.py to a minimum version via FTP, which used to work fine, but now boot.py on the WiPy isn't changing, and the file I've copied over by FTP is present but just called boot - anybody know what causes this please?

[Roberthh]

Maybe the file sytem's space on WiPy is exhausted, it is pretty small. That's what happens to me frequently. Try to delete a file and redo the copy.

[jgmdavies]

Thanks for the tip Robert, but I deleted most of my files on the device and I still get that 'boot file problem'. I also tried going back to 1.8.3 but no change.

[Roberthh]

"Boot file problem" means: you cannot download boot.py? Maybe it's locked by your host computer somehow. That's why I use command line ftp, since file manager sometimes behave unexpected.

You could also try to do a factory reset via GP28 and then reinstall the recent firmware. But be careful. There are people who damaged their WiPy by accidentally shortening 3.3 V (see viewtopic.php?f=11&t=1348&p=8284&hilit=GP28#p8260), even if that should not be possible.

[Roberthh]

As another test to remove all posssible sources of disturbance, you could remove all jumpers which connect wipy to the USB/Serial device on the expansion board. If the ISR problem still persists, then compared to my setup I see only three topics left:

- the power supply through USB and expansion board
- the expansion board
- the WiPy itself. That seems unlikely since other people have the same trouble.

[jgmdavies]

Thanks Robert - I'll try more experiments. "Boot file problem" meant I can't update boot.py - it seems to download to the WiPy, but becomes just 'boot', alongside the unchanged 'boot.py'. It used to work! I'm using a commercial FTP product that's never failed me.

Is anyone else monitoring this and trying the Timer/irq experiments with 1.8.3 or 1.8.4?

[Miguel]

I do.

- MicroPython v1.8.4-10-g081c064 on 2016-09-13; WiPy with CC3200
- factory default boot.py
- empty main.py
- extension board
- Belkin microUSB power supply

Your test script hangs immediately after pasting to REPL.

Michal

[Roberthh]

My primitive set-up (w/o expansion board) continues to run. This morning I thought it had stopped at 86399, but that was just the telnet session, which has a timeout at 86400 seconds. Restarting telnet showed the counter still ticking at 110000 + x.
B.T.W.: This means that either my boot.py or main.py ist not empty. At least it sets a longer session timeout. looking for every difference, I'll post the command this evening. Looking in the old posts her, it should be something like:

Code: Select all

from network import server
s = server(timeout=86400)