Has anyone used the Azure Nx MQTT Client ?

[T J]

How can I fix this issue ?

Error: Invalid Register Name for _ipsr ( can't find ipsr)

#ifndef TX_MISRA_ENABLE
 
register unsigned int _ipsr __asm("ipsr");
 
#endif

[Haithem Rahmani]

Hi @Community member​ 

Did you have a look at the Nx_MQTT_Client on github, it is working correctly without any build issue.

BTW where is this piece of code located?

regards

Haithem.

[T J]

hi, Haithem

that code is in the tx_port.h file.

what is the use of the cube setup if it doesn't work ?

Microsoft came back and said,

"Looks like you are using the ARM Compiler 5 (ac5) port. Please use the GCC (gnu) port."

"These also sound like project configuration issues. Please contact ST support for help with this project."

do you have any clue how to revert to that ?

Nick

[Haithem Rahmani]

Hi @Community member​ 

>what is the use of the cube setup if it doesn't work ?

Sorry I didn't catch your point, did you check the above-mentioned project?

Could you share more details about your env.?

• Which IDE are you using?
• Are you using the STM32CubeMX to generate the project?
• If yes could you share your .ioc project file?

regards

haithem.

[T J]

Please check this thread,

This is the error, this is the code,

Can you try to compile this yourself ?

@Haithem Rahmani​ 

[T J]

hi,

its a shame it takes so long to get your response.

Which time zone are you in ?

GMT +10 here

I have done this many times already,

I will start again

I will download RKOUSTMRelease of X-CUBE-AZRTOS-H7 v2.0.1

Which folder should that go ?

C:\Users\Poco\STM32Cube\Repository ?

(not under C:\Users\Poco\STM32Cube\Repository\STM32Cube_FW_H7_V1.9.0)

ok, a fresh download, now Azure 2.0.1 and compile

 

where is the Cube file ?

why is it not included in the folder ?

ok, generating a new cube file from scratch in this folder, is this correct ?

C:\Users\Poco\STM32Cube\Repository\x-cube-azrtos-h7-main\Projects\STM32H735G-DK\Applications\NetXDuo\Nx_MQTT_Client

Just selecting the board H735, and start project with default peripherals is this correct ?

enabled multi threaded support

OK, selecting a new folder for the new project: is this correct ?

C:\Users\Poco\STM32Cube\Repository\x-cube-azrtos-h7-main\Projects (project name MQTT5)

Generate files

ok, done, Cube file attached

Open Visual Studio

new GDB project

import from Keil

nono with floating point support

and compile

with this result:

so either way the results are the same,

Yesterday I was following the Getting Started Video and selecting the Azure software set inside the cube

the cube decided to use the Azure 1.0.0 files and it downloaded them to compile and give the fails I reported 2 days ago.

I had to buy the H735-DK to suit that video.

Maybe you can try to reproduce this with a fresh cube file and compile ?

I hope you can resolve this.

Please give me a step by step on how you load and compile to zero errors.

[Haithem Rahmani]

The Azure RTOS is not natively supported by STM32CubeMX, but via Softaware packs rather.

regards

Haithem.

[T J]

@Haithem Rahmani​ can you please compile this code from the cube and make it work and let me know what I am missing because it doesnt work.

I am using ther 735DK unit which is supported by the cube Azure.

[Haithem Rahmani]

Hi @Community member​ 

here is the link to github repo with all applications there:

https://github.com/STMicroelectronics/x-cube-azrtos-h7/tree/main/Projects/STM32H735G-DK/Applications/NetXDuo/Nx_MQTT_Client

You can clone it, and compile the project for your preferred toolchain.Then you can check what's wrong with your own project settings.

regards

Haithem.

[T J]

@Brian Jacobsen​ can you look at this code for me ?

I need someone to recompile from the cube from scratch using the 735DK kit which is supported

[Tesla DeLorean]

Really do need to get your out-of-the-box software experience working a lot better.

Not sure what the focus is on there, but so much support resources are wasted on stuff that should just work.

And not just on your own boards, but those which are also popular. Some actual testing, and building for real-world implementations, would make the boiler-plate code generation more robust, which honestly seems an essential step to being seen as a serious tool.