- Notifications
You must be signed in to change notification settings - Fork 119
Move supported microcontroller boards into standalone section #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… and move more detailed mcu info under internals Signed-off-by: Ron Evans <ron@hybridgroup.com>
Signed-off-by: Ron Evans <ron@hybridgroup.com>
| Reading over it, seem sensible enough. 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Two nits, but other than that looks good to me.
Also, maybe we should mention somewhere that TinyGo can also be used as a regular Go compiler? Some people may assume it only works for microcontrollers while it works just fine on Linux. This PR seems to remove the section that says this.
| | SPI | YES | YES | | ||
| | I2C | YES | YES | | ||
| | ADC | YES | Not yet | | ||
| | PWM | YES | Not yet | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The hardware does not natively support PWM. It can of course be emulated in software.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
content/microcontrollers/pca10031.md Outdated
| | SPI | ? | No | | ||
| | I2C | ? | No | | ||
| | ADC | ? | No | | ||
| | PWM | ? | No | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The nrf51822 and nrf51422 are almost identical (the difference is support for certain wireless protocols). I think it is safe to assume the support is equivalent to nrf51822.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But PWM is not directly supported?
(The nrf51x22 seems to have a hardware trick for it using timer/PPI/GPIO, though. But no direct support.)
…orrectness Signed-off-by: Ron Evans <ron@hybridgroup.com>
Signed-off-by: Ron Evans <ron@hybridgroup.com>
| Also added a section for Linux, so people know it exists. I think this is now ready for merge. |
| | ||
| # TinyGo on Linux | ||
| | ||
| TinyGo also lets you compile programs for Linux systems, both 32-bit and 64-bit, on both x86 and ARM architectures. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the ARM architecture there is Cortex-M, maybe add "(Cortex-M)" after the "ARM" there?
Saying because (these days) when I see mention of ARM, I personally mostly think of ARM64 as that's one of the primary deployment targets I do with stuff in mainline Go. 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There might be big Cortex-M chips that support Linux, but in general Linux is run on the Cortex-A family of processors. Cortex-M is the microcontroller family of processors.
TinyGo supports both the 32-bit and 64-bit variants on Linux so saying "ARM" should in theory be enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. 😄
| Well, when we add that support, we can modify the site further. I was actually thinking there will end up a whole subsection under Linux. But for now, I think we should leave it. |
| Ok, looks good to me! |
| OK, then go ahead and merge and I will deploy. |
| OK, since this PR was reviewed by both @aykevl & @justinclift I will just merge myself this time. Thank you! |
| Something that I only see now: the digispark has no hardware support for UART. Maybe there is some support in the "universal serial interface" it implements (basically hardware support for any kind of serial interface, but no full UART peripheral). |
This PR reorganizes supported microcontroller boards into standalone section. It also moves the more detailed mcu info that was previously there under "compiler internals"