Keil uVision 5 Optimization Level 3 for LPCOpen Library

[lpestanas]

Hi LPC Community,

I am porting the New LPCOpen Library 18xx->43xx for Keil uVision.

I am using the LPC4330FBD144 as my device and will be coded on Keil uVision.

My code works fine on Optimization 0 and 1 with no warnings and build errors.

But when I tried Optimization 2-3, the program would hang up with no changes in the code.

Is the new LPCOpen DFP 3.02 tested with Optimization Level 3 on Keil uVision?

I already read the Application Note 202, 298 for MDK ARM compiler optimization and it is quite tedious to check for "volatile" on variables, applying __attribute__((used)) on functions to be skipped and we are not allowed to use #pragma on actual program deployment of the firmware to isolate the hanging part. Please advise if someone tested it with Optimization Level 3 and they succeeded with no hangup or faults. 

Thanks and Good Day,

Leo Pestañas

[ZhangJennie · Accepted solution]

Hi lpestanas

LPCOpen is developed and only tested with default compiler optimization setting.  

Anyway if anyone ever tested with other level of optimization, welcome input.

Jun Zhang 

[lpestanas]

Hi Zhang,
Thanks for the response.
This will mean that I should also consider migrating the library to Optimization Level 3.

Best Regards,
Leo

[ZhangJennie]

yes. correct.

[lpestanas]

Hi Zhang,

Given that LPCOpen is an open-source,

a. did NXP released a driver that was tested across Optimizations (let us say Optimization level 0. 1. 2 and 3)?

b. Is the user of LPCOpen allowed to alter the contents to make it Optimization Level 3 without any software licensing implications regardless of purpose whether it will be a commercial or personal use only?

Best Regards,
Leo

[ZhangJennie]

HI lpestanas,

We don't have driver  tested across Optimizations.

LPCOpen copyright is anounced as below which should answer your question. You can also find this file under LPCOpen install folder.

Thanks,

Jun Zhang