Skip to main content
SHATE.1
SHATE.1
Associate III
November 12, 2020
Solved

I-CUBE-LRWAN Projects do not have .ioc files

  • November 12, 2020
  • 2 replies
  • 2817 views

Why each project in the I-CUBE-LRWAN expansion Package are not provided with .ioc file for an easy customisation to a different board !!!

ST complicate life and impossible to find the solution to well do the job. please help!!!

 

In the UM2285 Developpment Guideline for STM32 expansion Packagethey say that each expansion Package must contain the .ioc file but in the i-cube-lrwan not the case!!!!! why?

Thanks for help

This topic has been closed for replies.
Best answer by Imen.D

Hello @SHATE.1​ ,

I-CUBE-LRWAN expansion Package was designed and its first release published before the guidelines you mentioned were enforced, and probably even before UM2285 document was written.

Its legacy structure is not compatible with STM32CubeMX and our teams are working on this to make a new version that can be integrated in a pack for STM32CubeMX.

Your request is raised internally and will be taken into account. But, currently, there is no short term planning defined yet to integrate .ioc file in the package.

Hope this answered your question.

When your question is answered, please close this topic by choosing Select as Best.

Imen

2 replies

Tesla DeLorean
Tesla DeLorean
Guru
November 12, 2020

It was built around the Semtech libraries, not ST's models, by actual developers, not a code generator.

If you want to integrate stuff, do it at the HAL level.

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
SHATE.1
SHATE.1Author
Associate III
November 12, 2020

Thank you for your quick answer

But How i can do it at the HAL level???? You know i'm not specialised in the soft development, i'm a Hardware engineer and i developped a custom board with STM32L476 and a Lora Module with the SX1262 semtech radio. in the i-cube-lrwan provided by ST there's an end node project around the STM32L476 but i want to configure the pins and it's very complicated because there's no .ioc file to do it graphically. i used STM32CubeMX to do that in the normal case and make my program after ( there's a good Hands-on explaining that on youtube) but an example of implementation of the LORAWAN stack in a custom board there's nothing!!

Thank you in advance

Tesla DeLorean
Tesla DeLorean
Guru
November 12, 2020

I don't know your background, I'm an EE, most of my class mates could code.

The CubeL4 repository should have example code/projects. You should be able to build code to drive your peripherals with CubeMX, and between the examples, and mechanically generated code you'll need to extract the HAL based functionality.

For the radio stuff, you're probably going to want find a close proxy, and then port the pin level specifics to your board. Perhaps clone an existing project, and then modify to match your hardware. Get the radio side working, then merge in the peripheral code.

Not sure there is a simple graphical method, you might need to pull an Embedded SW Engineer into the project.

Tips, Buy me a coffee, or three.. PayPal VenmoUp vote any posts that you find helpful, it shows what's working..
I
Imen.DAnswer
Technical Moderator
November 17, 2020

Hello @SHATE.1​ ,

I-CUBE-LRWAN expansion Package was designed and its first release published before the guidelines you mentioned were enforced, and probably even before UM2285 document was written.

Its legacy structure is not compatible with STM32CubeMX and our teams are working on this to make a new version that can be integrated in a pack for STM32CubeMX.

Your request is raised internally and will be taken into account. But, currently, there is no short term planning defined yet to integrate .ioc file in the package.

Hope this answered your question.

When your question is answered, please close this topic by choosing Select as Best.

Imen

"When your question is answered, please close this topic by clicking ""Accept as Solution"".ThanksImen"
Terms & ConditionsAccessibility statement