I am debating the use of J-Link Commander versus J-Flash in a production environment. I realize that Segger provides comments that J-Link Commander is not recommended for Production.
With J-Link Base, I am able to flash and test my product. Everything seems to work fine. What exactly are my risks or concerns with this setup?
I understand that J-Flash has the benefit of controlling some of your standalone flash products. This does not apply to my environment. I am using J-Link Base.
There are comments to the affect that J-Flash and/or the SDK provides more customization. My environment is working and I do not require, apparently, the extra customization capabilities. I should mention that I intend to have multiple J-Link Base programmers connected to a single PC, and will be programming in parallel with the use of the J-Link Commander "-SelectEmuBySN" feature. This item I have not tested out on multiple units, yet..
J-Flash is optimized for speed in some manner different than J-Link Commander, but my programming speeds are very reasonable at this time.
There is a "double CRC check" feature in J-Flash, explained as "double CRC check to make sure that cases where the data in the flash itself is also protected via a CRC, does not cause any trouble.", which stands out a real difference between the program sequencing. My device does not utilize CRC on the entire image, so this feature is not useful.
In summary, J-Link Commander seems to be a fine solution for me, but the many references to "not recommended for production" continues to bug me. Again, can you detail any risks or concerns with my use of J-Link Commander for my described environment that I should be aware of? Thanks.
Three related threads I found useful:
[ANSWERED]J-Link flash download available for free or not?
[ANSWERED]Parallel flashing with J-Link Commander
forum.segger.com/index.php?form=PostAdd&threadID=2816
With J-Link Base, I am able to flash and test my product. Everything seems to work fine. What exactly are my risks or concerns with this setup?
I understand that J-Flash has the benefit of controlling some of your standalone flash products. This does not apply to my environment. I am using J-Link Base.
There are comments to the affect that J-Flash and/or the SDK provides more customization. My environment is working and I do not require, apparently, the extra customization capabilities. I should mention that I intend to have multiple J-Link Base programmers connected to a single PC, and will be programming in parallel with the use of the J-Link Commander "-SelectEmuBySN" feature. This item I have not tested out on multiple units, yet..
J-Flash is optimized for speed in some manner different than J-Link Commander, but my programming speeds are very reasonable at this time.
There is a "double CRC check" feature in J-Flash, explained as "double CRC check to make sure that cases where the data in the flash itself is also protected via a CRC, does not cause any trouble.", which stands out a real difference between the program sequencing. My device does not utilize CRC on the entire image, so this feature is not useful.
In summary, J-Link Commander seems to be a fine solution for me, but the many references to "not recommended for production" continues to bug me. Again, can you detail any risks or concerns with my use of J-Link Commander for my described environment that I should be aware of? Thanks.
Three related threads I found useful:
[ANSWERED]J-Link flash download available for free or not?
[ANSWERED]Parallel flashing with J-Link Commander
forum.segger.com/index.php?form=PostAdd&threadID=2816