Skip to content

Conversation

@deadprogram
Copy link
Member

This PR reorganizes supported microcontroller boards into standalone section. It also moves the more detailed mcu info that was previously there under "compiler internals"

… and move more detailed mcu info under internals Signed-off-by: Ron Evans <ron@hybridgroup.com>
Signed-off-by: Ron Evans <ron@hybridgroup.com>
@justinclift
Copy link
Member

Reading over it, seem sensible enough. 😄

Copy link
Member

@aykevl aykevl left a 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 |
Copy link
Member

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

| SPI | ? | No |
| I2C | ? | No |
| ADC | ? | No |
| PWM | ? | No |
Copy link
Member

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.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

Copy link
Member

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>
@deadprogram
Copy link
Member Author

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.
Copy link
Member

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. 😄

Copy link
Member

@aykevl aykevl Jan 10, 2019

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.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. 😄

@deadprogram
Copy link
Member Author

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.

@aykevl
Copy link
Member

aykevl commented Jan 10, 2019

Ok, looks good to me!

@deadprogram
Copy link
Member Author

OK, then go ahead and merge and I will deploy.

@deadprogram
Copy link
Member Author

OK, since this PR was reviewed by both @aykevl & @justinclift I will just merge myself this time.

Thank you!

@deadprogram deadprogram merged commit 4b35e42 into master Jan 11, 2019
@aykevl
Copy link
Member

aykevl commented Jan 11, 2019

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).

@deadprogram deadprogram deleted the feature/collect-internals branch May 14, 2019 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

4 participants