Why are the 2.0 libraries so inconsistent?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Why are the 2.0 libraries so inconsistent?

583 Views
intertronic
Contributor II

Hi everyone,

 

you create a complete new library and from start there is no future view on the libraries.

For example your make freertos drivers for interrupt-drivers (uart, spi, i2c) but in the structures there is no place for dma functions. If there will come a dma-rtos-driver in the future the structures will be complete different from now. So we have to rework all projects depending on this ksdk.

 

The smartcard driver is complete different from all the others, there is some sort of generic interface.

 

Why are the rtos-drivers are not lose-coupled?

Why was the chance for a good new library not used?

 

Regards

Labels (1)
1 Reply

398 Views
ivadorazinova
NXP Employee
NXP Employee

Hi Josef.

Thank you for your feedback.

It works by this way because it is so designed.

It is not recommended to port from older KSDK versions to KSDK 2.0 because of structure changes.

Have a nice day.

Best Regards,

Iva

0 Kudos
Reply