This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RL ARM libs 4.5 source code

It seems to happen with every update of the MDK IDE that previous applications are broken ( eg either the file_config.c is changed to look or use new #defines etc).

When I got 4.5 I simply just placed the new precompiled libs in the project to get things working again as I was in a hurry.

I have now found time to sort out the code repositry and looking a the source code for RL I see its not been updated since 4.23 and there does not appear to be an update available.

I belive I have the right license to have the source ode and have been waiting for the RL updates to appear as they have done in the past eg get the MDK update and a couple of weeks later out come the RL Libs updates.

Does anyone have a later version of RL ARM than 4.23 or an I going to have to jump through hoops again eg NDA signed again.

Thanks

Parents
  • Hello,

    I would like to clarify a few things on behalf of Keil/ARM.

    1. The source code publishing policy changed with the introduction of MDK-Professional with MDK v4.20 in March 2011. ARM signed agreements with existing RL-ARM customers to give them access to the RL-ARM source code for a transition period that ended on 31 Dec 2011.

    2. The source code for the Flash File system, USB Host&Device and TCPnet components is available with a tiered pricing structure for Singe Product, Single Product Line and Multiple Product Line use. The exact pricing can be obtained from local distributors and is very competitive when compared to other commercial offerings.

    3. The source license is NOT a per seat license. We require a MDK-Professional license for every developer using the sources, but that requirement can be rescinded for larger orders to remain competitive.

    That being said, I understand that it can be frustrating when a product that you have become used to stops being available (or changes price and licensing), but these changes happen. The MDK-Professional product is very successful in the market and is being sold to independent developers, small and big companies alike.

    We have no intention to "silently drop" the product or keep our customers from using it - in that case we wouldn't invest into expanding the middleware offering, as has recently happened for NXP LPC1800/4300 and Freescale Kinetis.

    Kind regards,
    Johannes Bauer
    ARM Keil Product Manager

Reply
  • Hello,

    I would like to clarify a few things on behalf of Keil/ARM.

    1. The source code publishing policy changed with the introduction of MDK-Professional with MDK v4.20 in March 2011. ARM signed agreements with existing RL-ARM customers to give them access to the RL-ARM source code for a transition period that ended on 31 Dec 2011.

    2. The source code for the Flash File system, USB Host&Device and TCPnet components is available with a tiered pricing structure for Singe Product, Single Product Line and Multiple Product Line use. The exact pricing can be obtained from local distributors and is very competitive when compared to other commercial offerings.

    3. The source license is NOT a per seat license. We require a MDK-Professional license for every developer using the sources, but that requirement can be rescinded for larger orders to remain competitive.

    That being said, I understand that it can be frustrating when a product that you have become used to stops being available (or changes price and licensing), but these changes happen. The MDK-Professional product is very successful in the market and is being sold to independent developers, small and big companies alike.

    We have no intention to "silently drop" the product or keep our customers from using it - in that case we wouldn't invest into expanding the middleware offering, as has recently happened for NXP LPC1800/4300 and Freescale Kinetis.

    Kind regards,
    Johannes Bauer
    ARM Keil Product Manager

Children
  • Thanks for clarifying, Johannes.

    On a positive note, my experience with Keil and MDK-ARM in terms of support for fixing library bugs and support for various platforms has always been prompt and very good. To report an issue with the TCP/IP-related components (as I have done on a few occasions) and to have a fix provided to us usually within 24 or 48 hours is very reassuring.

  • Johannes

    It would reassure me more if I knew I had a working example I could refer of something that closer to a real world application.

    To be honest your examples of using the Libs are very poor. Fine for showing a single lib at a time ( and only more recently 2 at once).

    Get your support to dev a project using RTX controlling a USB host MSD and also being able to log data to a SD card on the system as well as communicating via TCP/IP to a third parties kit.

    Have Data thats used by the TCPIP updated by the content of the USB MSD.

    ( No its a not a project I need - but if you feel you must add CAN and all the mashings that go with it (eg transport protocol and BCM support) and get the emWin going all together and you might be closer ;) )

    My experience of knitting together the RTX, FS and USB controlling a host MSD was not the best in the world and especially dissappointing in regards to USB Lib. If you want more detail I am happy to provide it in private.

    To me having the source code was about saving time. If there is a problem now I feel I would have to jump through hoops to prove something wasnt right time that could be spent elsewhere.

    Now I have to decide what do we do about the tools and libs.

    Interview without coffee is the order of the day I think

    Danny