gh-raspberrypi/pico-sdk

Watch

Why using ARM Core M and doing an Espressif style? #522

New issue

Closed

opened 2021-07-20 15:27:40 -05:00 by schreinerman · 1 comment

schreinerman commented

2021-07-20 15:27:40 -05:00

(Migrated from github.com)

Can somebody explain, why the Raspberry Pico has an ARM Core M but does not follow the ARM Core M software standards? So the SDK does not implement the benefits of ARM Core M and therefore is not compatible to the ARM Cortex M Eco-System, third parties, etc.? The big advantage of IP in the todays world is you getting hardware and software by the IP vendor - in this case the MCU Core by ARM. So why just using the hardware and the interesting part "Software" is ignored?

So nice SDK, but as soon a product with Pico comes to mass production, I see a lot of costs up-coming, because defined interfaces to third parties, tool suppliers, etc. are not existing. So for everything extra costs are required.

I was very happy to see Raspberry Pi foundation has an own MCU but as soon it came to software I was disappointed.

Can somebody explain, why the Raspberry Pico has an ARM Core M but does not follow the ARM Core M software standards? So the SDK does not implement the benefits of ARM Core M and therefore is not compatible to the ARM Cortex M Eco-System, third parties, etc.? The big advantage of IP in the todays world is you getting hardware and software by the IP vendor - in this case the MCU Core by ARM. So why just using the hardware and the interesting part "Software" is ignored? So nice SDK, but as soon a product with Pico comes to mass production, I see a lot of costs up-coming, because defined interfaces to third parties, tool suppliers, etc. are not existing. So for everything extra costs are required. I was very happy to see Raspberry Pi foundation has an own MCU but as soon it came to software I was disappointed.

schreinerman commented

2021-07-21 04:43:14 -05:00

(Migrated from github.com)

Thanks for this statement.

Thanks for this statement.

Sign in to join this conversation.

No labels

can't reproduce

code cleanliness

compiler version issues

hardware_clocks

hardware_exception

hardware_watchdog

needs reporter detail

newlib-multicore

pico_async_context

pico_binary_info

wifi integration

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-raspberrypi/pico-sdk#522

No description provided.