support for NUCLEO L496ZG
Hi all -
I'm evaluating CrossWorks for a new project my company is undertaking. It's been several years since I've looked at IDEs for embedded systems and the like, so I'm more than a bit rusty. I do like what I've seen of Crossworks so far. I've watched the tutorial on YouTube for getting started. It's very well done, but the author is using a slightly different model of the NUCLEO board than what I have. As a result, I'm unable to connect to my board from the "Targets" window. I searched for a BSP for this board, but couldn't find one. Does anyone know of a resource for this?
I'd appreciate chapter and verse on getting such a resource integrated into CrossWorks, as I'd like to complete my evaluation this week. Thanks in advance for any assistance.
-
Hello Michael,
do you have installed the driver for the ST-Link? You can get them from the ST-Website.
https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-utilities/stsw-link009.htmlBest Regards
-
Hello Michael,
when you are using the onboard-Target-Interface you should connect via ST-Link/V2 (or try ST-LINK if this is not working)
If you are using a J-Link adapter from Segger, you must download the drivers from here: https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack
Install it and set the Path to the JLink_x64.dll (if you use the 64-Bit Version of CrossStudio)
Regards
-
Oh yes, of course. I got the onboard target interface working (at least I can step through the debugger now).
I've installed the SEGGER driver, and updated the path in the Target Properties.I still get an error message (a different one now) about "Failed to connect to target. No idcode detected." Is this because the J-Link isn't connected to a board?
Thanks for the help.
-
Hi Markus - I'm trying to do a tutorial (the one that involves blinking a LED). It appears that I still need to install a BSP for my particular NUCLEO, but I don't see one for the Nucleo-L496ZG in the Package Manager (I looked both the STMicro and the CrossWorks section. Do you have a recommendation for how I should proceed? The tutorial says I should use the generic ARM PU support package, but that will require modification. I'd prefer to get something up and running as quickly as possible, to show management that we have a solution for building and testing code on this board. From there, I can then work on adapting whatever package I use for the board we're producing.
-
Hello Michael,
the STM32L496ZG on the Nucleo-L496ZG is supported by the STM32 CPU Support Package:
Check the long list of supported Targets on the right
You don’t need a BSP for a particular Board. The ones for the used Controller are sufficient
Regards
Markus
-
OK, I installed that package without incident. I found a sample project "dbugio" which consists of two asm files and one C file. My attempt to build it results in errors "attempt to use an ARM instruction on a Thumb-only processor." It opens the asm files in the editor as well. I have "ARM Debug" selected in my Project Explorer. What am I missing?
I don't know if this example is going to do much anyway, as it seems to perform file manipulation, but if I can get it to build, then I can go find the LED blink example for another board and just copy the code into here.
Thanks.
-
I don’t know a project with this Name, but you can easily create a new Project for your Board:
File -> New Project
Choose in the „New-Project“-Wizard “An executable for ST Microelectronics STM32”, Choose a name and press next.
In the next-Window select your Target Processor: STM32L496ZG.
After Finishing the Dialog, you have created a Project for the Controller on your Evaluation Board.
You will find lots of examples in the STM32CubeL4 Package
Check also this Video from Rowley:
https://www.youtube.com/watch?v=-GcWhUdXCYI&feature=youtu.be
Regards
-
Now that's pretty slick. (That video was very helpful.)
I notice that the import put main.c and other files into a folder called Application/User instead of the Source Files folder; is this an artifact of importing a project?
And, I assume that if I can find a project with FreeRTOS built in, I could do the same with that?
Thanks...it feels like I'm finally getting somewhere.
-
Hi Markus,
I have a related question. Can you please share the code in the video tutorial? The blinking LED.
My board is different, and I am using JLink.
-
Hello Markus,
Thanks for your note.
For a different board ( or better say, microchip from the family of ATSAMD51G19A) how should I find the source files that Cross Studio understands?
I see that you used #include <ctl_api.h> this header file to use the function:
ctl_board_set_leds(1);
How can I find the corresponding header file for my microchip?
Thanks,
Sam.
-
Hello SAM,
Rowley provides Board-Support-Package only for Evaluation-Boards. As far as I understand there is no Evaluation-Board for the D51, but you can use the Board-Support-Package for the E54 (https://www.rowleydownload.co.uk/arm/packages/index.htm?https://www.rowleydownload.co.uk/arm/packages/Atmel_ATSAME54-XPRO.htm) as a starting point. There is also a blinky example included.
You can change the Target-Controllers in the project-properties.
Best Regards
-
Hi Markus,
I get this up and running (LED), and now I am in need of expert opinion for sending messages through USART TX. Please take a look at the Question page in this website I made (How-send-a-message-to-RX).
Thanks,
https://rowley.zendesk.com/hc/en-us/community/posts/360046718972-How-send-a-message-to-RX
-
Hello Sam,
I don´t have access to the Rowley-Ticket-System. So I don’t see your request. However, Rowley should help you there if you have a valid license.
In general, you can create sample-code for your board via this web-service from Atmel:
Best regards
Markus
Please sign in to leave a comment.
Comments
18 comments