Difference between revisions of "Custom RAMCode SDK (discontinued)"
Line 1: | Line 1: | ||
− | Before announcing the Open Flashloader concept, SEGGER offered a so called custom RAMCode SDK which could be used to create custom RAMCodes. These RAMCodes were supported in J-Flash / stand-alone mode, only (no J-Link DLL / IDE support). The custom RAMCode concept has been replaced for certain reasons by the much more flexible Open Flashloader concept in 2016 |
+ | Before announcing the Open Flashloader concept, SEGGER offered a so called custom RAMCode SDK which could be used to create custom RAMCodes. These RAMCodes were supported in J-Flash / stand-alone mode, only (no J-Link DLL / IDE support). The custom RAMCode concept has been replaced for certain reasons by the much more flexible Open Flashloader concept in 2016. |
+ | |||
+ | '''NOTE:''' Custom RAMCode support has been removed from J-Flash since software version V7.54 (2021). |
||
For details regarding the Open Flashloader, please refer to [[Open_Flashloader | SEGGER Open Flashloader]]. |
For details regarding the Open Flashloader, please refer to [[Open_Flashloader | SEGGER Open Flashloader]]. |
Revision as of 17:04, 14 December 2021
Before announcing the Open Flashloader concept, SEGGER offered a so called custom RAMCode SDK which could be used to create custom RAMCodes. These RAMCodes were supported in J-Flash / stand-alone mode, only (no J-Link DLL / IDE support). The custom RAMCode concept has been replaced for certain reasons by the much more flexible Open Flashloader concept in 2016.
NOTE: Custom RAMCode support has been removed from J-Flash since software version V7.54 (2021).
For details regarding the Open Flashloader, please refer to SEGGER Open Flashloader.