cancel
Showing results for 
Search instead for 
Did you mean: 

STM32L4 HAL package

ivan2
Associate II
Posted on June 28, 2015 at 22:27

Hi All,

We are adding support for new STM32 devices to

http://visualgdb.com/

- our Visual Studio plugin for embedded development, and it looks like the new STM32L4 devices don't have a HAL package available yet. Is it possible to download a pre-release HAL package somewhere? We would love to integrate it into VisualGDB to let our customers experiment with it.
11 REPLIES 11
l239955_stm1
Associate II
Posted on June 29, 2015 at 06:57

Hi, I was in the STM training last week and they tell me that L4 HAL support will be in the autumn.

ivan2
Associate II
Posted on June 29, 2015 at 18:47

Hi,

Thanks for your reply. BTW, do you know any official contact at ST that could clarify whether they could share the pre-release HAL before the Autumn? I'm asking because some of our customers are inquiring about L4 support already and would love to try it out before the official release.

Posted on June 29, 2015 at 18:59

Find a local representative

http://www.st.com/stonline/contactus/contacts/index.php

Or submit an ''Online Request''

http://www.st.com/web/en/support/online_support.html

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
ivan2
Associate II
Posted on June 29, 2015 at 23:30

Hi,

Thanks for the links, however unfortunately the support page does not work (always shows ''Invalid User ID or Password.'' even in the private mode as suggested there) and the local contacts list distributors and sales, but no technical contacts. Is there any other way of contacting the guys who could give some clarifications about the pre-release HAL?

Posted on June 30, 2015 at 00:46

This is primarily a user forum, ST does not participate here a lot, I will kick the moderator. You could also try the forum where the Cube people tend to hangout, or at least a very small subset of them. [DEAD LINK /public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx]https://my.st.com/public/STe2ecommunities/mcu/Lists/STM32Java/AllItems.aspx

I don't know if ST has a mandate forbidding staff and FAE's participating here, but generally they don't. The internet does however provide a number of ways of finding them.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Posted on June 30, 2015 at 00:57

Prods moderator and off-board contacts....

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Amel NASRI
ST Employee
Posted on June 30, 2015 at 12:30

Hello All,

A Cube package is generally released with the official announcement of the product.

It cannot be made available for all users when it is in beta release.

As suggested by Clive1, when the package isn't yet released officially, a Customer has to  contact his FAE or local distributor.

In this particular case, if the target is to anticipate the integration of CubeL4 in VisualGDB, it may be confusing for users the fact of sharing a non-official package.

Best Regards

-Mayla-

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Posted on June 30, 2015 at 16:57

I guess it's one of those awkward chicken-egg situations, you really need to provide support to Tool Developers. Perhaps you can provide Ivan with the same contacts that liaise with Keil, IAR, et al. While I understand the he's not a ''customer'' of the parts, his tools service/enable customers that would normally fit under the distrbutor/fae model.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
ivan2
Associate II
Posted on July 03, 2015 at 05:56

Hi,

Thanks a lot for clarifying this. Your concern is understandable, as people may expect release quality from such a package.

Just one last question: would it help if we added a big disclaimer message (and would require the users to agree with your EULA clearly stating that it's a beta) or any other warning message you would require? Or do you believe this could still confuse the end users about the quality to expect?