Re: Prog12z Programmer V 167
Marika Posley
PROG12Z also includes the command-line version of the programmer software, called CPROG12Z, which allows scripted programming. Together PROG and CPROG are useful for development, production line programming, or field firmware upgrades. For a more full-featured production solution, P&E also offers a stand-alone, in-circuit flash programmer called the Cyclone PRO that is ideal for production programming and field maintenance.
PEmicro's PROG12Z Flash Programmer software allows you to program/reprogram both internal and external HC12 or MC9(S)12(X) flash devices in-circuit, via any of PEmicro's BDM interfaces(available separately). The programmer software communicates with the processor's Background Debug Mode module through a PEmicro Debug Interface
The LAB eShop is part of ISS Group, based in Stockholm, Sweden, and works with suppliers from all over the world to ship and support tools to the electronic companies and professionals across continental Europe.
Note: The Cyclone Pro is no available. It has been replaced by the Cyclone Universal and Cyclone Universal FX production programmers. These programmers support all of the devices supported by Cyclone PRO
In the chapter Device Characteristics and links to documentation, can be found supported devices by USBDM and useful links for the USBDM devices where are described, for example, compatible IDEs and other useful information.
P&E's PROG12Z Flash Programmer software allows you to program/reprogram both internal and external HC12 or MC9(S)12(X) flash devices in-circuit, via any of P&E's BDM interfaces(available separately). The programmer software communicates with the processor's Background Debug Mode module through a P&E Debug Interface , which connects a communication port of a PC (Serial, Ethernet, USB, and Parallel interfaces are all available) to a 6-pin BDM connector on the target system.
PEmicro's PROG flash programming software allows the user to program/reprogram external flash devices in-circuit, via one of PEmicro's compatible hardware debug probes. The debug probe connects the USB port of the PC to the target header. The programming software can then talk to the target processor via debug mode.
The license that activates PROG will reside on a Multilink debug probe. The user who activates the software will choose a Multilink on which to permanently install the license. The allows that Multilink to work with PROG on any machine where a supported version of the software is installed. No license is required to use PROG software with Cyclone programmers, as the Cyclone includes PROG software.
There is a variety of PROG software available; each version supports a different MCU architecture. To see if the device you are interested in is supported, please view the corresponding programming algorithm list. PROG will include this library of algorithms.
There is also a CRPROG executable included which allows the user to create programming scripts to automate the programming process. A separate CPROG user manual details the procedure for scripted programming.
PEmicro supports both internal flash and flash connected to an MCU via the SPI, I2C, and Address/Data bus interfaces. Programming algorithms must make assumptions about how the flash is connected to the MCU, but if these assumptions are off, the "Chip Select Diagnostics Mode" in our PROG software can help the user determine what changes may need to be made to the programming algorithm to match their device setup. Read more about how to use Diagnostics mode:
A trial edition is available for PEmicro's PROGPPCNEXUS Flash programming software. Download 64K Starter Edition at no cost and request an installation code. This version has a 64KB code size limit for programming.
PEmicro's PROG12Z Flash Programmer software allows you to program/reprogram both internal and external HC12 or MC9(S)12(X) flash devices in-circuit. The programmer software communicates with the processor's Background Debug Mode module via any of PEmicro's compatible Multilink debug probes or Cyclone programmers (available separately). These connect the PC to a 6-pin BDM connector on the target system.
PROG12Z also includes the command-line version of the programmer software - CPROG12Z. Together they are perfect for development, production line programming, or field firmware upgrades. Packages that include both software and a hardware interface are available here.
I already got a .s19 file and only want to program a couple of MC9S12XEP100CAG chips and unlikely to need to do it again so looking for most cost effective solution. What type of programmer do I need and are any aftermarket options available? My chips are soldered to the boards but I don't see any apparent programming headers there so I plan to connect directly to the pins of the chip. Please help.
I am really confused of your S19 record. I do not understand how you get the srecord you use. The addresses are in logical form and because of this suitable for HiWave. No conversion to linear form is necessary. However, as I wrote before, there is no address FD4000 in the memory map.
The cureent s19 file uploads to 88%. If I manually changed the addresses of the remaining 12% of the code would the code still work? Would you recommend which adresses could I use? I wish I understood about that but all this is new to me and not easy to understand. I would appreciate the help.
OK, i have forgotten linear format for stand alone devices. It looks like you use HiWave and try to use S19 record in linear format which was generated for stand alone device. In this case I suggest you to use reverse conversion from linear format to a banked and it should work.
MODC should by connected to the VDD via 4.7k resistor. MODB and MODA should be connected to GND to select special single chip mode for communication with the hiwave or pemicro sw. (of course, rest should also be connected .... see -MagniV-Microcontrollers/Reference-schematics-for-S12-X-devices/ta-p...
scheamtic for s12XE and look at the connection of the pins PE5, PE6. They can be conneced to GND directly if they are not used for another purpose later in the application.
)
The connector is not necessary if you are able to ensure connection of required circuitry.
Thanks a lot. What about connecting +5V power to the s12xe is that pin 87 (VDD)? Can +5V be connected directly to the pin or is a capacitor necessary? And which pin is the s12xe ground for powering it for programming?
Hi, so I found the BDM connector on my board and connected to it via USBDM programmer and hiwave. When I press select my .s19 file and press load code it starts uploading and when it reaches some 80% it gives an error: 'Error while writing to FD4000...FD4200. Information: no memory at this address.' I tried many times on 2 different boards with same chip: MC9S12XEP100CAG but every time it starts and then fails. I attach my .s19 file if anybody could help me please as I have no idea what is wrong.
Hi, my board does not have a BDM connector, can I connect directly to the relevant pins or do I need to connect via some resistors? Looks like I have the package as in the picture. Could you please help identify the BDM pins: VCC, GND, RESET and BKGD?
Thank you for checking, I appreciate it. The .s19 file I attached is the official firmware that the ECU diagnostic tool uses to flash onto this chip via CAN BUS. But when upgrading the firmware there was some sort of error and flashing did not finish essentially bricking the ECU as the diagnostic tool can no longer connect to the chip via CAN. So I am trying to flash the .s19 file on this chip via BDM. How could then the .s19 file be not correct? Also could it be that the .s19 file part that is wrong is not actual program but something that could be removed? I mean would it be possible to convert the file to leave the data only? Thank you
another question: the the value of FSEC register is 0xFE. it means that MCU is unsecured and the backdoor access is disabled.
is it necessary to enable the backdoor access before securing operations?
One more approach for "confusing"....It is for S12G but the approach is the same (S12G is very simplified S12XE which is master device of the 180nm technology devices from S12XE family, like XEG, XHY, XS,...).
If you're using our PROG12Z software or the Cyclone Image Creation utility, the command to engage security is "SD". It should program 0xFC to the NVSEC byte in flash to secure the device. This will disable all access to RAM/FLASH/EEPROM via the BDM BKGD pin. The only way to restore access is a mass erase of the flash (unless your application implemented a backdoor access key). When we erase the device, we always force NVSEC to 0xFE so you don't secure the device everytime you reset it in our software. The "SD" command should be placed at the end of your programming sequence.
I use multi-link programmer and i dont have Cyclone Image Creation utility software.
A- can i use CHIPSECURE command (or any commands) instead ?
(if A is right) is it correct: in> CHIPSECURE SETUP 0xFF0F 0x3 0x1? // SET SEC[1.0] field in FSEC to secure
(if A is wrong) B- does Cyclone Image Creation utility support multi-link programmer?
(if B is right) how can i get the Cyclone Image Creation utility software.
no, backdoor unsecure doesn't involve flash erase/reprogram. After backdoor unsecure MCU stays unsecured until reset (power cycle, reset pin, COP, etc). If you want permanently unsecure, then yes, you need to manipulate NVSEC (0x7F_FF0F) bits erasing reprogramming flash sector. But 1) backdoor unsecure has nothing to do with it and 2) it's not possible if NVPROT bits are set to protect NVPROT location (0x7F_FF0C, see Table 27-3. Flash Configuration Field). Anyway manipulating top flash sector, which includes reset vector is like shooting into you own foot, sudden power loss at bad time and you get dead unit in the field.
Backdoor unsecure allows temporary (until first reset) BDM (BKGD pin) access to RAM/FLASH/EEPROM. Backdoor unsecure is there to avoid erasing or reprogramming anything, as well avoid unprotecting write protected FLASH when you need just temporary debug access to secured MCU.
7fc3f7cf58