Sles 9 I386 Rc5 Cd1 Isogenics

Nov 25, 2012  Hi All, I suspect the old SLES 10 SDK ISOs are still in the novell download site. The issue is getting a link that points to them. The search method does not find them anymore. Similarly for early SLES 10 and SLED 10 the search method fails but I have direct links to them that still exist in other places on the Novell website. I only want these early versions to test upgrade methods from early. SLES-9-SP-1-i386-RC5-CD3.iso 36e798f4868aece793b592c3d0f05e62 The images can be written to a blank CD-R. To do that on a Linux system, we recommend to use the program cdrecord. A sample command line to cdrecord looks like this: cdrecord dev=0,4,0 -v -eject -speed=8 SLES-9-SP-1-i386-RC5-CD1.

Protected FLASH Pages with Processor Expert Failed Programming with protected FLASH If I try to re-program the protected bootloader with Segger J-Link (both in CodeWarrior and Eclipse/KDS with GDB), then the download silently fails. The effect is that somehow the application on the board does not match what it should be. Looking at the Console view, it shows that erase has failed (but no real error reported):-(: Jlink: Failed to erase sectors 0 @ address 0x00000000 (Algo135: Flash protection violation. Flash is write-protected.). ERROR Algo135 Flash Protection Violation about failed FLASH Programming What I need is to unprotect the memory and then erase it. Erasing The Segger J-Link features a very fast programming.

Part of that speed is that the Segger firmware checks each FLASH page if it really needs to be programmed, and only then it erases and reprogrammed that page. So downloading twice the same application actually will not touch the FLASH memory at all. Additionally, it does not do a complete erase of the device: it only programs the pages I’m using in my application.

The advantage of that is first speed. And it does not erase the application data I’m using in non-volatile memory (see ““). However, sometimes I really need to clear all my data in FLASH too, and then I need to erase all my FLASH pages on the device.

Unlocking and Erasing FLASH with Segger J-Link. Posted on October 5, 2014 by Erich Styger. This entry was posted in ARM, CodeWarrior, CPU's, Debugging. Segger J Flash Arm Keygen Cracks. UpdateStar is compatible with Windows platforms.

Segger has product named ‘J-Flash’ which is used to Flash and Erase devices outside of an IDE. There is a free-of-charge ‘Lite’ version available for download from Segger.

This utility is not intended to be used for production. With this utility I have a GUI to erase and program my device. Erasing Device with Flash File to Target Again, this does not work if the device is locked. CodeWarrior has another feature called ‘Target Task’ which can be used to erase/unsecure (if your device is supported), see ““.

So I need to use a different tool to unlock and unprotect my device: the J-Link Commander. Unlocking and Erasing with J-Link Commander To unlock the device, Segger has a utility named ‘J-Link Commander’, available from. The binary is ‘jlink.exe’ on Windows and is a command line utility. To unlock the device use unlock Kinetis.

Unlocking and Erasing with J-Link Commander Summary In order to re-program the protected FLASH sectors with Segger J-Link, I need first to unlock and mass erase the device. For this, there is the J-Link Commander utility which has a command line interface to unprotect and erase the device. For erasing only, the J-Flash (and Lite) is a very useful tool, especially to get a ‘clean’ device memory. To me, the Segger way and tools are very powerful. In this case, things are very flexible, but not that obvious. So I hope this post can help others to get his device unlocked and erased. Happy Erasing 🙂.

Hi Erich, I am trying to use similar procedure as yours to “erase my secure Kinetis KV31 device”, I use J-link utility – unfortunately I can’t erase it due to device is secured. J-Link>unlock Kinetis Found SWD-DP with ID 0x2BA01477 Unlocking deviceO.K. J-Link>erase Erasing device (MKV31F512xxx12) ****** Error: Failed to erase sectors 8 @ address 0x00004000 (Algo135: Flash pro tection violation.

Flash is write-protected.) Info: J-Link: Flash download: Total time needed: 1.155s (Prepare: 0.689s, Compar e: 0.000s, Erase: 0.067s, Program: 0.000s, Verify: 0.000s, Restore: 0.398s) ERROR: Erase returned with error code -5. J-Link>Is there a way to unlock secured device and erase it? I am OK with deleting my flash I just want to reprogram device again. Thanks for you advice. HI Erich I Had the “Device is secured” problem on 2 of 5 MKV31F devices.

Using universal multilink i had no way to unlock it,and the odd thing is that one of the devices was new,so i was not able to flash it for the very first time.The project that i tred to load was working fine with other boards let’s call it “A_project”. I built an almost empty project,let’s call it “Dummy” and i have found a difference in Hex files: In A_project the byte ad address 0x40C=0x7E and in “Dummy” 0x40C=0xFE.,at least the SEC bits were Unsecured,i will check why i haveKEYEN Field= Backdoor key access disabled Furthermore the reset pin toggles continously(it has 10K to VDD,100nF to GND). I dont ‘have a Segger J-Link,but almost for shure i should have some demo board with a J_Link on board. Motorola drivers.

Do you think i can do something? This is a 100 pins IC,and i ‘m am scared that after changed it by hand,i could face the same problem. Many thanks once more.

Hi Diego, yes, using a J-Link might work for you. The ‘real’ J-Links have stronger pull down circuit I think so would be better.

But give it a try. Ultimately, I always have J-Link at hand for these kind of things. The reason why you see the reset pin toggling is that the device is continuously resetting: it starts, then runs into a hard fault, restarts again, etc. You might try as well to pull down (e.g. Push button) the reset line while you connect to the target.

This would give the debug probe a chance or larger time window to connect to the microcontroller and halt it. You migt try this several times. I hope this helps, and good luck! Request Letter Format For Gratuity Calculator. No, there is no utility for this as far as I know. So in your case the reset pin is still active after power-up until it reads the FOPT register. With JTAG you can reset the device using the JTAG command.

So if you are using JTAG, you should be able to connect. If you only have SWD, then you need to be able to connect with the debugger during this tiny window. So I would try to debug it while the microcontroller is powered up.

You might need 10, 50, 100 or more tries, but I think this is what you can do. The other way is that you add a button to the reset pin and pull it to GND. Give it a try. Dear Erich, regarding your post I’m having a similar problem with internal KE02 EEPROM.

Price: €498.00 ARM/Cortex and Renesas RX Debug Probe with Ethernet Interface Includes unlimited Flash breakpoints (Flash Breakpoints), the ARM Remote Debug Interface (RDI), remote GDB server for the GNU Project Debugger (GDB Server), Flash Loaders, and software to program internal and external flash of your microcontroller (J-Flash). Ultra Fast ARM/Cortex and Renesas RX Debug Probe Based on the highly optimized and proven J-Link, it offers even higher speed. Includes unlimited Flash breakpoints (Flash Breakpoints), the ARM Remote Debug Interface (RDI), remote GDB server for the GNU Project Debugger (GDB Server), Flash Loaders, and software to program internal and external flash of your microcontroller (J-Flash). Software Enhanced ARM/Cortex and Renesas RX Debug Probe Includes unlimited Flash breakpoints (Unlimited Flash Breakpoints), the ARM Remote Debug Interface (RDI), remote GDB server for the GNU Project Debugger (GDB Server), Flash Loaders, and software to program internal and external flash of your microcontroller (J-Flash). Price: €298.00 Software Enhanced ARM/Cortex and Renesas RX Debug Probe Includes unlimited Flash breakpoints (Unlimited Flash Breakpoints), the ARM Remote Debug Interface (RDI), remote GDB server for the GNU Project Debugger (GDB Server), Flash Loaders, and software to program internal and external flash of your microcontroller (J-Flash). ARM/Renesas RX Debug Probe ARM/Cortex Debug Probe, and Renesas RX Debug Probe.

No power supply required (driven and powered through USB). J-Link GDB Server license is now included.

ARM/Renesas RX Debug Probe ARM/Cortex Debug Probe, and Renesas RX Debug Probe. No power supply required (driven and powered through USB). J-Link GDB Server license is now included.

SUSE LINUX Enterprise Server 9 (x86, AMD64 & EM64T) and Novell ZENworks 6.6 Linux Management
Download Instructions

The SUSE® LINUX Enterprise Server 9 is available as a set of twelve ISO images.

FilenameMD5 Checksum ValueApprox. File Size
SLES-9-i386-RC5-CD1.isocc419d86f3f5ff99395ca4de9d967600265.1 MB
SLES-9-i386-RC5-CD2.iso86e97184aae42ba6013ea7460372ffe5611.3 MB
SLES-9-i386-RC5-CD3.isof880b3ba92fc43add18259c9437f648d580.8 MB
SLES-9-i386-RC5-CD4.isobc7b88f34a8142bacbdd4d1fddd3fc50545.6 MB
SLES-9-i386-RC5-CD5.iso7844c76fc9f39a2af9ef6751ec18af60649.5 MB
SLES-9-i386-RC5-CD6.iso9e0fdd835e52f53906dff110515eb002648.2 MB
SLES-9-x86-64-RC5-CD1.iso1fb270a7123895abc846a377c3d1dfdd246.2 MB
SLES-9-x86-64-RC5-CD2.iso1579c82c85fe71b4cc68685d638c883d603.1 MB
SLES-9-x86-64-RC5-CD3.iso5330a150eb51542d378dbe281f2315a2411.8 MB
SLES-9-x86-64-RC5-CD4.isoa9d5b0dddd45f378f97ea9bca2b12b11488.8 MB
SLES-9-x86-64-RC5-CD5.isodc6de0d488e4dbf6aef322f7aadba7dd644.7 MB
SLES-9-x86-64-RC5-CD6.iso2324e164faab72df89e4078b6a7c1aec648.6 MB

The Novell® ZENworks® 6.6 Linux Management software is available for download as a single ISO image.

FilenameMD5 Checksum ValueApprox. File Size
zlm-6.6.0-v4.isoda4663f8a4d9761560bbaf2754f15824272.0 MB

NOTE: Do not burn the .iso file to CD. Burn the contents of the .iso file (the .iso image) to CD.

Download Instructions

Sles 9 I386 Rc5 Cd1 Isogenics
  1. Click the Download button next to the .iso file you want to download, then follow the prompts to download the file to either a local or network directory.

  2. Repeat Step 1 to download the .iso file for each software component you want.

  3. Validate the integrity and completeness of the ISO. MD5 checksum instructions are listed below.

  4. Use your CD burning software to burn CDs of each of the images.
    NOTE: Do not burn the .iso file to CD. Burn the contents of the .iso file (the .iso image) to CD.

MD5 checksum instructions

Md5Sums are used to establish the integrity and completeness of the downloaded ISO

On Windows

  1. Obtain MD5SUM from one of the links below.

  2. md5sum <isoname.iso>'. For example, this command will be:

    md5sum zlm-6.6.0-v4.iso

  3. The md5sum program will process the file and produce the checksum. Sauer and sohn side by side numbers type.

  4. Compare this MD5 checksum with that listed above.

On Linux:

  1. Use md5sum which should be included with your Linux distribution

  2. md5sum <isoname.iso>. For the ZENworks 6.6 Linux Management ISO this command will be

    md5sum zlm-6.6.0-v4.iso

  3. The md5sum program will process the file and produce the checksum.

  4. Compare this MD5 checksum with that listed above.


Installation Instructions

SUSE LINUX Enterprise Server 9 Installation instructions are contained in the SUSE Linux Enterprise Server Administration Guide.

Novell ZENworks 6.6 Linux Management Installation instructions are contained in the ZENworks 6.6 Linux Management Administration Guide.

Additional Information

The following links provide additional information:

A trademark symbol (®, ™, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.