I ran the IDE a few times, now Mac says the app can't be opened

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

I ran the IDE a few times, now Mac says the app can't be opened

Jump to solution
1,536 Views
JimDon
Senior Contributor III

So why is this?

Off to a real bad start here.,

0 Kudos
1 Solution
1,515 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Any chance we can have the workspace log attached here? Also, more details about your Mac system would be helpful. Unfortunately, the error doesn't say much...

Is it the same behavior as in the following community thread [1] ?

Or maybe it's the Eclipse bug referred in [2]?

Regarding the potential broken code signature, please also take a look at [3].

Regards,
MCUXpresso IDE Support

[1] https://community.nxp.com/t5/MCUXpresso-IDE/MCUXpressoIDE-Code-Signature-Invalid-exception-when-laun...

[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=578883

[3] https://developer.apple.com/forums/thread/684509 

View solution in original post

5 Replies
746 Views
min-eta
Contributor I

I have had a similar problem with both MCUXpresso 11.7.1 and 11.8.0 on Mac OS 13.6 (Ventura). The IDE would be installed, and I would work on some sample projects. Then after a few days, the IDE would not load. It may be related to some OS updates? or XCode update? I really can't be sure until I can investigate if it happens again.

I fixed it by reinstalling MCUXpresso (WITHOUT uninstalling).

As to whether it is related to reported bugs [1] or [2] above? It sounds like it could be either [1] or [2] to be honest.

0 Kudos
1,507 Views
JimDon
Senior Contributor III

I used the Pin configurator to move the LED to GPIO_AD_B0_03 - still no blinky.

I threw the scope on and indeed D8 is toggling at a 1 second rate, and according to the UM that is where the LED is.

So UM says the LED is connected to D8 which is GPIO_AD_B0_03 which D8 is indeed this pin, 

 

Ok I found the issue unlike what the UM thinks and the SDK thinks, the :LED is connected to GPIO_AD_B0_08, from the B1 version schematic.

So the fix for  blinky with the B1 board is, you need to toggle this pin. If you go into the Pin configurator, if you untag 09 as USER_LED and tag this pin as USER_LED the code will work.

 

FWIW I learned a ton going thru this so I am kinda glad.

 

Turns out there is an SDK for the B rev, but is it not marked as such. The new SDK worked fine with blinku.

0 Kudos
1,512 Views
JimDon
Senior Contributor III

I have some other issues, but when I tried to submit a ticket I got an error (which let me submit a ticket about the error)

Here is one issue:

The Blinky code for the RT 1060 EVB does not blink. (since this is the sanity check, it should work!)

The SDK version seems to imply that it is for the A version of the board, but the one I just purchased seems to be the B version (not sure about this).

The UM for the boards (Rev 0,7 1/22) calls this pin out as GPIO_AD_B0_03 which in the NXP naming.

The Code is this in the example:

#define BOARD_USER_LED_GPIO                                                GPIO1   /*!< GPIO peripheral base pointer */

#define BOARD_USER_LED_GPIO_PIN                                               9U   /*!< GPIO pin number */

#define BOARD_USER_LED_GPIO_PIN_MASK                                  (1U << 9U)   /*!< GPIO pin mask */

#define BOARD_USER_LED_PORT                                                GPIO1   /*!< PORT peripheral base pointer */

#define BOARD_USER_LED_PIN                                                    9U   /*!< PORT pin number */

#define BOARD_USER_LED_PIN_MASK                                       (1U << 9U)   /*!< PORT pin mask */

It seems the code downloads and runs correctly as I can step thru it.

At this point I have no idea how the NXP name relates to the ARM sdk names.

Any idea if this is correct, and if not what should it be?

Thanks for looking into this....

 

 

0 Kudos
1,513 Views
JimDon
Senior Contributor III

Thank you for you quick response!

So sorry I uninstalled and reinstalled, but if it happens again I will check these its.

[1] It was not the code sig for me, as it had ran before. Ventura does have some changes in this area, but I am on Monterey.

[2] I will look for item 2 and see if that happens.

[3] I did not get permission complaints, as I had ran it before.

0 Kudos
1,516 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Any chance we can have the workspace log attached here? Also, more details about your Mac system would be helpful. Unfortunately, the error doesn't say much...

Is it the same behavior as in the following community thread [1] ?

Or maybe it's the Eclipse bug referred in [2]?

Regarding the potential broken code signature, please also take a look at [3].

Regards,
MCUXpresso IDE Support

[1] https://community.nxp.com/t5/MCUXpresso-IDE/MCUXpressoIDE-Code-Signature-Invalid-exception-when-laun...

[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=578883

[3] https://developer.apple.com/forums/thread/684509