1 of 1 people found this helpful
A similar issue - Creating a dual-core application in Modus for the 416045-02 module
Unfortunately, there is no new update over this issue and cm0+ is still not available for general user in MTB2.x.
This is very disappointing and confusing, especially when this functionality is still advertised on the PSOC 6 main page and several documents still online.
Furthermore, the MTB 2.0 release notes doesn't mention this restriction, while this functionality was available on MTB 1.1 (I just ran a blinky app on the M0 core of my CY8CPROTO-062-4343W board, compiled with MTB 1.1).
Is there any technical reasons for preventing users to use the second core? (concurrent bus access issues?)
Well, it took a little time but I finally managed to run and debug the entire network stack on the M0 core, with MTB 2.0.
I understand that this configuration is not supported, but my main concern is the product that we must release this year.
Moving to a faster MCU from another manufacturer is not an option, as while they are quicker they also need much more energy.
I just need to know if there’s a reason this solution is less reliable than when the code is executed on the M4.
Understand you concern. cm0+ not exposed does not mean it's less reliable to run the code on it. It's just a strategy to simplify the application process through not exposing it to customer.
It's fine for you to enable cm0+ by yourself. Cypress will evaluate it to make the decision of enabling dual cores.