wasp-os: MicroPython for PineTime!

[VMMainFrame]

  Pinetime-log2.png (Size: 330.11 KB / Downloads: 580)
  Pinetime-log3.png (Size: 125.89 KB / Downloads: 568)
  Pinetime-log4.png (Size: 271.05 KB / Downloads: 564)
Daniel,

I typed in the commands you gave me and it failed the same place as yesterday.  I then tried a few things and found that the /flash filesystem seems to already exist, and it has a file in it.  I also found if I umount it then it will mount without error.  See the attached screenshots.

Hugh

[danielt]

Daniel,

I typed in the commands you gave me and it failed the same place as yesterday.  I then tried a few things and found that the /flash filesystem seems to already exist, and it has a file in it.  I also found if I umount it then it will mount without error.  See the attached screenshots.

Hugh

Strange... so in summary everything appears to work perfectly! Thus it is *very* strange the watch doesn't show the UI automatically at boot.

I guess as a final check you should use cat('/flash/main.py') to make sure that the contents of main.py are correct. Perhaps you could also confirm that you are not acidentally booting into safe mode are you (if you have the button pressed when the pine cone disappears to the final time then the watch will enter safe mode and skip the startup file).

Anyhow... either way, thanks for your contributions. I've already improved the bootloader based on your feedback and today I filed another issue based on our conversation (since it would be so much better if safe-mode was obvious and I didn't have to ask the last question): https://github.com/daniel-thompson/wasp-os/issues/29 .

[lupyuen]

Hi @danielt: I'm almost done documenting my wasp-os experiment on Mynewt, please have a look...

https://lupyuen.github.io/pinetime-rust-...icropython

I'm stuck with a multitasking conflict between wasp-os and Mynewt... wasp-os runs the REPL loop forever, scheduling its own tasks. But Mynewt needs to run the Event Loop to handle NimBLE Bluetooth packets.

Any idea which part of wasp-os I should modify to feed the Mynewt Event Loop?

Alternatively I could start another Mynewt task to run wasp-os, but that would consume extra memory (for the stack). Plus extra overheads for task switching. Thank you so much :-)

[VMMainFrame]

Daniel,

I typed in the commands you gave me and it failed the same place as yesterday.  I then tried a few things and found that the /flash filesystem seems to already exist, and it has a file in it.  I also found if I umount it then it will mount without error.  See the attached screenshots.

Hugh

Strange... so in summary everything appears to work perfectly! Thus it is *very* strange the watch doesn't show the UI automatically at boot.

I guess as a final check you should use cat('/flash/main.py') to make sure that the contents of main.py are correct. Perhaps you could also confirm that you are not acidentally booting into safe mode are you (if you have the button pressed when the pine cone disappears to the final time then the watch will enter safe mode and skip the startup file).

Anyhow... either way, thanks for your contributions. I've already improved the bootloader based on your feedback and today I filed another issue based on our conversation (since it would be so much better if safe-mode was obvious and I didn't have to ask the last question): https://github.com/daniel-thompson/wasp-os/issues/29 .

I issued the cat command and an ls command and the results are confusing, considering the information I previously provided.


  Pinetime-log5.png (Size: 320.82 KB / Downloads: 584)

[danielt]

Strange... so in summary everything appears to work perfectly! Thus it is *very* strange the watch doesn't show the UI automatically at boot.

I guess as a final check you should use cat('/flash/main.py') to make sure that the contents of main.py are correct. Perhaps you could also confirm that you are not acidentally booting into safe mode are you (if you have the button pressed when the pine cone disappears to the final time then the watch will enter safe mode and skip the startup file).

I issued the cat command and an ls command and the results are confusing, considering the information I previously provided.

Yes, confusing indeed.

I think to get to the bottom of this I think I'll need to change to the code to boot.py to get some more information out. IIRC you were using the 0.2 release... are you compiling yourself or working just with the binary release? Just wondered if I should share patches or .zip file?

PS Since we're getting to the point of throwing code around this might also be a good point to migrate the discussion to the github issue tracker for wasp-os? Attachments work out better there...

[danielt]

Hi @danielt: I'm almost done documenting my wasp-os experiment on Mynewt, please have a look...

https://lupyuen.github.io/pinetime-rust-...icropython

I'm stuck with a multitasking conflict between wasp-os and Mynewt... wasp-os runs the REPL loop forever, scheduling its own tasks. But Mynewt needs to run the Event Loop to handle NimBLE Bluetooth packets.

Any idea which part of wasp-os I should modify to feed the Mynewt Event Loop?

Alternatively I could start another Mynewt task to run wasp-os, but that would consume extra memory (for the stack). Plus extra overheads for task switching. Thank you so much :-)

Sorry for the delay. I'm afraid missed this when I looked at the forum yesterday.

To keep things robust you probably need to deeply integrate this into Micropython rather then the wasp-os code.

I'd consider adding an implementation of MICROPY_VM_HOOK_LOOP to the MyNewt port that handles pending MyNewt events. This allows will dispatch the events from the main VM execution loop and will share the processor regardless of what Python code we are running. Note that this code is a really, really hot path so needs to be written for maximum performance. That usually means a divisor so the hook does not for every virtual opcode, take a loop at ports/esp8266/mpconfigport.h for an example.

After that you'd probably also need to call the MyNewt event loop from mp_hal_stdin_rx_chr() as well since most implementation of micropython just stop dead in that function when they are seeking user input! This code is less performance critical because is mostly runs a human speed however for simplicity I think it would be OK to call MICROPY_VM_HOOK_LOOP here as well.

---

A simpler alternative that would probably also work is to dispatch MyNewt events from mp_hal_stdin_rx_char(), machine_deepsleep and machine_lightsleep. That would rely on the system calling one of the sleep functions when it want to save power (which wasp-os does).

[lupyuen]

Thanks Daniel! Lemme peek at those functions and experiment some more [emoji3]

Sent from my Pixel 4 XL using Tapatalk

[VMMainFrame]

Strange... so in summary everything appears to work perfectly! Thus it is *very* strange the watch doesn't show the UI automatically at boot.

I guess as a final check you should use cat('/flash/main.py') to make sure that the contents of main.py are correct. Perhaps you could also confirm that you are not acidentally booting into safe mode are you (if you have the button pressed when the pine cone disappears to the final time then the watch will enter safe mode and skip the startup file).

I issued the cat command and an ls command and the results are confusing, considering the information I previously provided.

Yes, confusing indeed.

I think to get to the bottom of this I think I'll need to change to the code to boot.py to get some more information out. IIRC you were using the 0.2 release... are you compiling yourself or working just with the binary release? Just wondered if I should share patches or .zip file?

PS Since we're getting to the point of throwing code around this might also be a good point to migrate the discussion to the github issue tracker for wasp-os? Attachments work out better there...

Daniel,

Yes, I was using the 0.2 file from your web page.  I have not compiled anything, I am using your binaries.

I can move this discussion to the github tracker.  Do you want me to open a new issue or add on to one that already exists?

Hugh

[danielt]

Yes, confusing indeed.

I think to get to the bottom of this I think I'll need to change to the code to boot.py to get some more information out. IIRC you were using the 0.2 release... are you compiling yourself or working just with the binary release? Just wondered if I should share patches or .zip file?

PS Since we're getting to the point of throwing code around this might also be a good point to migrate the discussion to the github issue tracker for wasp-os? Attachments work out better there...

Yes, I was using the 0.2 file from your web page.  I have not compiled anything, I am using your binaries.

I can move this discussion to the github tracker.  Do you want me to open a new issue or add on to one that already exists?

That's fine. I can share .zip files for testing. Let's start a new github tracker. As it happens there is another "black screen" issue but it was fixed and AFAICT is completely unrelated to what you are seeing.

Feel free to post a link to the github issue on the forum so anyone else who's following this thread (or stumbles across us in a search engine six months from now) can join us if they wish.

[VMMainFrame]

Yes, confusing indeed.

I think to get to the bottom of this I think I'll need to change to the code to boot.py to get some more information out. IIRC you were using the 0.2 release... are you compiling yourself or working just with the binary release? Just wondered if I should share patches or .zip file?

PS Since we're getting to the point of throwing code around this might also be a good point to migrate the discussion to the github issue tracker for wasp-os? Attachments work out better there...

Yes, I was using the 0.2 file from your web page.  I have not compiled anything, I am using your binaries.

I can move this discussion to the github tracker.  Do you want me to open a new issue or add on to one that already exists?

That's fine. I can share .zip files for testing. Let's start a new github tracker. As it happens there is another "black screen" issue but it was fixed and AFAICT is completely unrelated to what you are seeing.

Feel free to post a link to the github issue on the forum so anyone else who's following this thread (or stumbles across us in a search engine six months from now) can join us if they wish.

I have opened issue 31 on the wasp-os github page. 

https://github.com/daniel-thompson/wasp-os/issues/31