Chip's presentation is now posted on the first link. I'll be working with future presenters to make the presentations more timely (1 hr) and precise. We had a bit of trouble getting started this time.
The delay need not take an instruction from the table.
Editing the source debug spin file could be a simple way to achieve the delay as usually when you're doing a debug you know what terminal you're using.
As far as I can see the Debug stub attached to your file will load itself into the ROM area move your program back to HUB 0 and then start COG0 with your program in Debug mode.
At that time it starts to spit out the first DEBUG serial, stating that it does start your program.
So there is no way to do it in your own source, your code is not running yet, you have to have a terminal open before your code runs, but after loading to the P2.
So the DEBUG loader stub has to wait for the HOST to switch from loading to terminal.
Hi, unfortunately I will not be able to see the presentation life. I would be interested in 2 questions:
1. When will micropython support programming all 8 cogs?
2. Micropython is said to be 200 times slower than C. What is the strategy to deal with this issue?
Good presentation!
Christof
1. Both Eric's Flexgui MicroPython and our Native P2 MicroPython allow you to start up addition cogs using the CPU method. The demo today will actually have 6 to 8 cogs running at various stages - the main MicroPython cog plus a mixture of Pasm2 cogs
2. Because of the above, you can put anything that needs speed in the additional 7 cogs. That takes the pressure off speeding up MicroPython immediately. MicroPython itself also has a variety of speedup options - there is a presentation from Damien about this that demonstrates this (including viper mode and various tricks). I'll post a link later
We're also interested in other ways to speed it up, its just not top priority at the moment
* About team oz
* About micropython
* About demo today
* Demo 1 – driving micropython from serial terminal
* questions
* Demo 2 – driving micropython from cross-platform mu editor
* More questions
* Demo 3 – advanced topics – live memory view, plotter
* Even more questions
* About team oz
* About micropython
* About demo today
* Demo 1 – driving micropython from serial terminal
* questions
* Demo 2 – driving micropython from cross-platform mu editor
* More questions
* Demo 3 – advanced topics – live memory view, plotter
* Even more questions
The youtube video Ken referred to can be viewed here:
I could do an hour on the new P2D2 hardware and aspects of the design and pcb including general tips on hardware design. Since my artwork of the P2D2r5 and P2PAL are completed and I am just finishing off the P2LAB, this might also be a good time for feedback and questions before the boards are made
I could do an hour on the new P2D2 hardware and aspects of the design and pcb including general tips on hardware design. Since my artwork of the P2D2r5 and P2PAL are completed and I am just finishing off the P2LAB, this might also be a good time for feedback and questions before the boards are made
So 1pm Wednesday PDT (7am Thurs AEST) .
P.S. I've penciled it in tentatively.
Great. I'll get a registration link up today and we'll get this in order for tomorrow.
Could you send me a picture of P2D2 PCB (or whatever you have, even a proto) plus a description of what's going to be discussed for the e-mail? We will put this together quickly.
Thanks Ken,
I'm still scratching my head with how I will start off
I think I will start with introducing the P2D2 as a P2 "breakout board" and a bit of the background that led to it, then quickly go through the on-board support functions and the rationale.
ITEM: P2D2 - what and why
SHARES: Photos of the pcb and view and zoom on sections of the schematic.
Then showing how the P2D2 module can be used as a stand-alone development board, or prototyping with matrix board, and as an embedded P2 module.
ITEM: Using P2D2
SHARES: Camera view of actual hardware.
ITEM: USB serial communications capabilities including loading new firmware.
SHARES: PC screen
After this I like to talk about the latest r5 revision board and the P2PAL layer as well as the P2LAB motherboard.
ITEM: New boards
SHARES: 3D pcb views, schematics.
Then I'd like to have time for questions and feedback, even requests for features etc since the artworks will all be going off together, but realistically probably not until next week which means I will have boards assembled by mid August.
So there is still time to add or change little things.
ITEM: Q&A
This morning I will check my setup here so I can use multiple cameras and make sure I can share some hires shots.
Last time I found I couldn't share these hires live images even though my download speed can be 200Mbps, the upstream could drop down to just a few Mbps, so I added another internet connection since then with a 40Mbs upstream capacity just for zoom.
Whooops! It's okay, I made a cutesy animated gif that's included in the e-mail already. Worry not; perfection is the enemy of a successful engineer (dare I say that here).
It'll be sent out to the 350 list subscribers in a moment.
TeamOz. How could there exist such a strong P2 nuclei in such a small population?
They're extra productive in winter. Hopefully they keep this going in their summer.
Great work, @"Peter Jakacki" ! I'm enthused for P2D2 and P2PAL (the R2D2 and C3PO of P2 land). It seems that you've thought of everything and the support of @jmg has also been useful for specifying parts. Chip once mentioned he has the Digi-Key catalog in his head.
Comments
Time in first post is set now to 2:00 pm Pacific. The Zoom setup is also for 2:00 pm Pacific.
At some point before today's Propeller 2 Live Forum we will post PNut and some code examples. I don't know when Chip will make those files available.
Ken Gracey
Ken Gracey
Eagerly waiting the youtube version- was not able to join until very late and everyone was going home!
Dave
Ken
Ken Gracey
CONstant for
DEBUG_TX_PIN and maybe for later use DEBUG_RX_PIN
also I think the quest for a start delay was not really solved.
Could be a CON too
Just insert a waitx #DEBUG_WAIT_START in the binary so we have a delay between installing the debugger and starting the main program in COG0.
So the HOST has time to close its download serial and open up PST or p2loads terminal serial port.
This would save @"Jeff Martin"'s problem with PropTool and PST as well as for all other loaders.
Enjoy!
Mike
He may not see this so I've copied it in an e-mail to him.
Ken Gracey
Editing the source debug spin file could be a simple way to achieve the delay as usually when you're doing a debug you know what terminal you're using.
As far as I can see the Debug stub attached to your file will load itself into the ROM area move your program back to HUB 0 and then start COG0 with your program in Debug mode.
At that time it starts to spit out the first DEBUG serial, stating that it does start your program.
So there is no way to do it in your own source, your code is not running yet, you have to have a terminal open before your code runs, but after loading to the P2.
So the DEBUG loader stub has to wait for the HOST to switch from loading to terminal.
Mike
https://mailchi.mp/866bd8a5204c/propeller-2-live-forum-chip-gracey-presents-spin-2-debug-with-runtime-expression-reporting-4484180
And make sure you've subscribed to our newsletter too! Promise not to try to sell you anything you don't need.
Ken Gracey
1. When will micropython support programming all 8 cogs?
2. Micropython is said to be 200 times slower than C. What is the strategy to deal with this issue?
Good presentation!
Christof
1. Both Eric's Flexgui MicroPython and our Native P2 MicroPython allow you to start up addition cogs using the CPU method. The demo today will actually have 6 to 8 cogs running at various stages - the main MicroPython cog plus a mixture of Pasm2 cogs
2. Because of the above, you can put anything that needs speed in the additional 7 cogs. That takes the pressure off speeding up MicroPython immediately. MicroPython itself also has a variety of speedup options - there is a presentation from Damien about this that demonstrates this (including viper mode and various tricks). I'll post a link later
We're also interested in other ways to speed it up, its just not top priority at the moment
Speaking of, I'm going to open the Live Forum in about five minutes.
Good morning to TeamOz!
Ken Gracey
* About team oz
* About micropython
* About demo today
* Demo 1 – driving micropython from serial terminal
* questions
* Demo 2 – driving micropython from cross-platform mu editor
* More questions
* Demo 3 – advanced topics – live memory view, plotter
* Even more questions
Ken Gracey
The youtube video Ken referred to can be viewed here:
So 1pm Wednesday PDT (7am Thurs AEST) .
P.S. I've penciled it in tentatively.
Great. I'll get a registration link up today and we'll get this in order for tomorrow.
Could you send me a picture of P2D2 PCB (or whatever you have, even a proto) plus a description of what's going to be discussed for the e-mail? We will put this together quickly.
Thanks!
Ken Gracey
I'm still scratching my head with how I will start off
I think I will start with introducing the P2D2 as a P2 "breakout board" and a bit of the background that led to it, then quickly go through the on-board support functions and the rationale.
ITEM: P2D2 - what and why
SHARES: Photos of the pcb and view and zoom on sections of the schematic.
Then showing how the P2D2 module can be used as a stand-alone development board, or prototyping with matrix board, and as an embedded P2 module.
ITEM: Using P2D2
SHARES: Camera view of actual hardware.
ITEM: USB serial communications capabilities including loading new firmware.
SHARES: PC screen
After this I like to talk about the latest r5 revision board and the P2PAL layer as well as the P2LAB motherboard.
ITEM: New boards
SHARES: 3D pcb views, schematics.
Then I'd like to have time for questions and feedback, even requests for features etc since the artworks will all be going off together, but realistically probably not until next week which means I will have boards assembled by mid August.
So there is still time to add or change little things.
ITEM: Q&A
This morning I will check my setup here so I can use multiple cameras and make sure I can share some hires shots.
Last time I found I couldn't share these hires live images even though my download speed can be 200Mbps, the upstream could drop down to just a few Mbps, so I added another internet connection since then with a 40Mbs upstream capacity just for zoom.
Many of us are looking forward to your update and the outline looks appropriate. Have an agenda and stick to it.
Be watching for links in the next hour.
Ken Gracey
Ken Gracey
Whooops! It's okay, I made a cutesy animated gif that's included in the e-mail already. Worry not; perfection is the enemy of a successful engineer (dare I say that here).
It'll be sent out to the 350 list subscribers in a moment.
Ken Gracey
https://mailchi.mp/5b68a4a6d9f1/propeller-2-live-forum-peter-jakacki-presents-p2d2
Ken Gracey
Thanks for the P2D2 presentation.
All your work is much appreciated.
They're extra productive in winter. Hopefully they keep this going in their summer.
Great work, @"Peter Jakacki" ! I'm enthused for P2D2 and P2PAL (the R2D2 and C3PO of P2 land). It seems that you've thought of everything and the support of @jmg has also been useful for specifying parts. Chip once mentioned he has the Digi-Key catalog in his head.
Ken Gracey
Ken Gracey