USBDM Activity
Debugging and programming interfaces for Freescale microcontroller
Brought to you by:
pgo-d
Activity for USBDM
-
Igor Maliszewski modified a comment on discussion Open Discussion
First - You are my hero :) it's working :) Secondly, for others: the correct template (Unfortunately, the engine of this website breaks the code when you upload it as text, you have to upload it as an image, Dennis's template was correct before being uploaded as text)
-
First - You are my hero :) it's worked :) Secondly, for others: the correct template (Unfortunately, the engine of this website breaks the code when you upload it as text, you have to upload it as an image, Dennis's template was correct before being uploaded as text)
-
First - You are my hero :) it's worked :) Second, for others, template with small corrections:
-
First - You are my hero :) it's worked :) Second, for others, template with small corrections: <device family="S12Z" name="MM9Z1J638"> <clock type="External"> <resetmethodsref ref="s12zResetMethods"> <erasemethodsref ref="s12zEraseMethods"> <memoryref ref="s12z8K_Ram"> <memoryref ref="FTMRZ_EEPROM_4K_4bS"> <memoryref ref="FTMRZ_PFlash0_SEC_128K_512bS"> <copctladdress value="0x06CC"> <sdidaddress value="0x0000"> <sdidmask value="0xFFFFFF00"> <sdid value="0x02070207"> <flashscripts> <tclscriptref ref="S12Z-FTMRZ-flash-scripts">...
-
Dennis Heynlein modified a comment on discussion Open Discussion
The flash loader does not appear to support EEPROM write operations. Here a Sample with USBDM TCL Interpreter Everything EEPROM Sector has a size of 32 Bit settarget s12z openbdm setdevice MM9Z1J638 reset NH connect halt ;#every EEPROM Word has its own ECC ;#erasing is only as double word possible ;#Erase 1 Sector (2 Words) rb 0x386 ;#FSTAT if CCIF == 0 Command is running wb 0x386 0x30 ;#FSTAT clear ACCERR & FPVIOL flag in flash status register wb 0x382 1 ;#FCCOBIX 2 COBs used wl 0x38C 0x12100000...
-
The flash loader does not appear to support EEPROM write operations. Here a Sample with USBDM TCL Interpreter Everything EEPROM Sector has a size of 32 Bit settarget s12z openbdm connect setdevice MM9Z1J638 reset NH ;#Erase Sector rb 0x386 ;#FSTAT if CCIF == 0 Command is running wb 0x386 0x30 ;#FSTAT clear ACCERR & FPVIOL flag in flash status register wb 0x382 1 ;#FCCOBIX 2 COBs used wl 0x38C 0x12100000 ;#FCCOB0+B1 0x12<<24 | 0x100000 COMMAND Erase Sector 0x12 and Address 0x100000 wb 0x386 0x80 ;#FSTAT...
-
The flash loader does not appear to support EEPROM write operations. Here a Sample with USBDM TCL Interpreter Everything EEPROM Sector has a size of 32 Bit settarget s12z openbdm connect setdevice MM9Z1J638 reset NH ;#Erase Sector rb 0x386 ;#FSTAT if CCIF == 0 Command is running wb 0x386 0x30 ;#FSTAT clear ACCERR & FPVIOL flag in flash status register wb 0x382 1 ;#FCCOBIX 2 COBs used wl 0x38C 0x12100000 ;#FCCOB0+B1 0x12<<24 | 0x100000 COMMAND Erase Sector 0x12 and Address 0x100000 wb 0x386 0x80 ;#FSTAT...
-
The flash loader does not appear to support EEPROM write operations. Here a Sample with USBDM TCL Interpreter Everything EEPROM Sector has a size of 32 Bit settarget s12z openbdm connect setdevice MM9Z1J638 reset NH ;#Erase Sector rb 0x386 ;#FSTAT if CCIF == 0 Command is running wb 0x386 0x30 ;#FSTAT clear ACCERR & FPVIOL flag in flash status register wb 0x382 1 ;#FCCOBIX 2 COBs used wl 0x38C 0x12100000 ;#FCCOB0+B1 0x12<<24 | 0x100000 COMMAND Erase Sector 0x12 and Address 0x100000 wb 0x386 0x80 ;#FSTAT...
-
The flash loader does not appear to support EEPROM write operations. Here a Sample with USBDM TCL Interpreter settarget s12z openbdm connect setdevice MM9Z1J638 reset NH ;#Erase Sector rb 0x386 ;#FSTAT if CCIF == 0 Command is running wb 0x386 0x30 ;#FSTAT clear ACCERR & FPVIOL flag in flash status register wb 0x382 1 ;#FCCOBIX 2 COBs used wl 0x38C 0x12100000 ;#FCCOB0+B1 0x12<<24 | 0x100000 COMMAND Erase Sector 0x12 and Address 0x100000 wb 0x386 0x80 ;#FSTAT clear CCIF bit - Start Write ;#Write Sector...
-
The flash loader does not appear to support EEPROM write operations. Here a Sample with USBDM TCL Interpreter **settarget s12z openbdm connect setdevice MM9Z1J638 reset NH ;#Erase Sector rb 0x386 ;#FSTAT if CCIF == 0 Command is running wb 0x386 0x30 ;#FSTAT clear ACCERR & FPVIOL flag in flash status register wb 0x382 1 ;#FCCOBIX 2 COBs used wl 0x38C 0x12100000 ;#FCCOB0+B1 0x12<<24 | 0x100000 COMMAND Erase Sector 0x12 and Address 0x100000 wb 0x386 0x80 ;#FSTAT clear CCIF bit - Start Write ;#Write...
-
my is the same
-
modification of s12z_devices.xml is sufficient I have also placed a 470nF between GND and Reset.
-
The flashloader is not optimal, but it works at first glance. I am currently trying to adapt the template to the S12Z of MM9Z1J638.
-
It is not the worst idea to reconnect the adapter before debugging.
-
It runs :) It's running, I just need to be able to understand what prevented it.
-
Hi, is it possible to debug a MM9Z1J638 with codewarrior 11 and USBDM ? The S12Z-core looks a bit like a MC9S12ZVH128. I can use USBDMScript with it. USBDMScript incorporating TCL - Copyright(c) 2011 Press ? for help % settarget S12Z USBDM DLL Version = 4.12.1.340 BDM List: 0 - USBDM-JS16-0001 : USBDM HCS08,HCS12,Coldfire-V1 BDM Found 1 devices S12Z % openbdm Opening USBDM-JS16-0001 BDM Version = HW=8D, SW=4C % connect :connect BDM status => Ackn, Speed-sync, Vpp-Off, Vdd-External, RSTO=1, No Reset,...
-
Read/Write Flash works. add this to C:\Program Files\pgo\USBDM 4.12.1.340\DeviceData\s12z_devices.xml <device family="S12Z" name="MM9Z1J638"> <clock type="External"> <memoryref ref="s12z8K_Ram"> <memoryref ref="FTMRZ_EEPROM_4K_4bS"> <memoryref ref="FTMRZ_PFlash0_SEC_128K_512bS"> <copctladdress value="0x06CC"> <sdidaddress value="0x0000"> <sdidmask value="0xFFFFFF00"> <sdid value="0x02070207"> <flashscripts> <tclscriptref ref="S12Z-FTMRZ-flash-scripts"> </tclscriptref></flashscripts> <flashprogramref...
-
Nedal Aljaber posted a comment on discussion Open Discussion
Hi DennisUnfortunately it still unsolved .Do you have any solution Nedal Yahoo Mail: Search, organise, conquer On Mon, 20 Jan 2025 at 12:49 pm, Dennis Heynleincl2k@users.sourceforge.net wrote: Did you get it to work? MM9Z1-638 Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/usbdm/discussion/1237993/ To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
-
Did you get it to work?
-
Peter O'Donoghue posted a comment on discussion Help
The MCF5216 is not supported by the USBDM programmer so I'm not surprised Unlock Now doesn't work. Are you using the MCF5213 selection in the programmer? A quick look at the MCF5126 manual in comparison to the MCF5213 chip (which is supported) shows that the MCF5126 does not support unlock using JTAG. It appears JTAG is used purely for the usual boundary scan operations? So don't expect Unlock Now to do much at all. If programming works then that is purely by chance. The MCF5216 appears similar to...
-
USBDM released /Version 4.12.1/Software/usbdm_4.12.1.340-1-x86_64.deb
-
-
-
-
Ano modified a comment on discussion Help
Someone in the NXP forum solved the question: [https://community.nxp.com/t5/OSBDM-and-TBDML/USBDM-making-full-flash-memory-dump-of-MC9S08AC96/m-p/1993740] Thanks!
-
Someone in the NXP forum solved the question I guess (although I still have to try it): [https://community.nxp.com/t5/OSBDM-and-TBDML/USBDM-making-full-flash-memory-dump-of-MC9S08AC96/m-p/1993740/highlight/true#M3967] Thanks!
-
Ok, I found that in the specifications it is stated PPAGE = 78, so I have to set it to 'paged memory' when reading. Now I can succesfully read PPAGE=0, PPAGE=1, PPAGE=2, PPAGE=3, see attached picture :-) . But I'm still not at 96K... Still missing is PPAGE=4 and PPAGE=5. Where are they hiding? If I set the address to 10000 - 13FFF and 14000 - 17FFF I get an error. Anyone?
-
Hi there, I'm trying to make a dump of the full flash memory of the MC9S08AC96 chip, which has a 96K FLASH memory. But I'm a bit confused by the memory map in the specifications: I can successfully make a dump of the flash memory in these ranges: 1870 - 3FFF (PPAGE=0), 4000 - 7FFF (PPAGE=1) and C000 - FFFF (PPAGE=3). When I verify the dump of these ranges it's successful. But that's only 42,896 bytes in total: I have the feeling I have to include other memory ranges as well to dump the entire flash...
-
-
-
-
-
Viktor modified a comment on discussion Help
Hi, I have board with MCF5216 . I use latest USBDM-CF board V3.1, latest firmware and software. I can read Flash memory with USBDM Memory dump utility. I can program and then verify new (blank) chip with CFVx Programmer. But I can't erase chip. The button Unlock Now ask me to enable JTAG and I did. I saw TCLK signal by oscilloscope. TCLK signal connected to CPU correctly. But chip still programmed. I found in description to USBDM: "Coldfire V2,3,4 These devices have a separate utility to unlock them...
-
Hi, I have board with MCF5216 . I use latest USBDM-CF board V3.1, latest firmware and software. I can read Flash memory with USBDM Memory dump utility. I can program and then verify new (blank) chip with CFVx Programmer. But I can't erase chip. The button Unlock Now ask me to enable JTAG and I did. I saw TCLK signal by oscilloscope. TCLK signal connected to CPU correctly. But chip still programmed. I found in description "Coldfire V2,3,4 These devices have a separate utility to unlock them so Mass...
-
Hi, I have board with MCF5216 . I use latest USBDM-CF board V3.1, latest firmware and software. I can read Flash memory with USBDM Memory dump utility. I can program and then verify new (blank) chip with CFVx Programmer. But I can't erase chip. The button Unlock Now ask me to enable JTAG and I did. I saw TCLK signal by oscilloscope. TCLK signal connected to CPU correctly. But chip still programmed. I found in description "Coldfire V2,3,4 These devices have a separate utility to unlock them so Mass...
-
Hi, I am no longer actively using the HCS08 version of the programmer so I can't comment immediately on your problems. I am also not using Windows any more so that also complicates matters. The error message indicates (obviously) that the programmer thinks you are trying to program using an image that lies outside of the programmable range of the target. There may be some other reason triggering this error or an code error that has crept in to later versions but I am not aware of any. I certainly...
-
Daniel posted a comment on discussion Help
Hello! I have a problem with my small research: i have target board with MCF5272 mcu and working BDM port. I’ve tried following: 1) I have bought freescale JM60-based debugger with 26-pin connector, and have installed USBDM firmware there. After several attemtps, i finally managed to connect to target board, but i am still unable to reach flash memory, because output dump is always empty. 2) I have found out, that old Coldfire chips don’t support async debug mode (as it was said in USBDM manual),...
-
Viktor Skvortsov modified a comment on discussion Help
-
hello! Have you solved the problem? I also can't flash or erase the MC9RS08KA8 controller. I have tried USBDM and Codewarrior software and the result is the same
-
-
-
Arturas12 posted a comment on discussion Help
help me
-
Hi all! I'm trying to erase the MC56F8035 processor with the USBDM 4.12.1.210 program and when I try to erase the processor it gives a TCL error, help me figure it out. Thanks
-
Hi all! I'm trying to erase the MC56F8035 processor with the USBDM 4.12.1.210 program and when I try to erase the processor it gives a TCL error, help me figure it out. Thanks
-
Hi all! I'm trying to erase the MC56F8035 processor with the USBDM 4.12.1.210 program and when I try to erase the processor it gives a TCL error, help me figure it out. Thanks
-
Look at the link on the main page USBDM Web Site
-
-
-
-
-
-
Edson David Marques modified a comment on discussion Help
I'm having problems copying and recording the MCF52235 microcontroller, I can't find its memory map! I'm using the USBDM MEMORYDUMP program! @win11. I'm sending attachments of the material I got, but I don't know how to interpret it!
-
I'm having problems copying and recording the MCF52235 microcontroller, I can't find its memory map! I'm using the USBDM MEMORYDUMP program! @win11. Estou enviando os anexos do material que consegui, porém não sei interpreta-lo!
-
I Need to read and write flash and data to MM9Z1-638 by USBDMLT what is the source code
-
Jim Gwaltney posted a comment on discussion Help
I have a MC9S08DZ32 that I need to write the eeprom data to (add. 0x1600 - 0x17FF)... I can write to the flash (0x7C00 - 0xFFFF) with a USBDMLT and flash programmer. What equipment / software to I need to write eeprom data? Thanks.
-
-
-
Dustin Sova posted a comment on discussion Help
Has anyone tried to update or add support for Cortex-M33 MCU's to the USBDMFlashProgrammer? Does anyone know if the hardware would even support it? For example Renesas RA6 devices.
-
Michele Me modified a comment on discussion Open Discussion
-
Hello everyone, I ask for help to be able to read this mcu SC511943CFN. Can anyone give me some pointers? I can't even find datasheets online. It is inside a bosch ecu. Thanks in advance to anyone who can help me..
-
fhgnv posted a comment on discussion Open Discussion
best hang on treestand a hang on treestand increases the hunter’s field of view, lesser chances are left to go home without a prized buck. As the best and most useful hunting utility for hunters, knowing this tool to its fullest is crucial.
-
Andrey Neshin posted a comment on discussion Help
Hello all. I am using the latest software and driver. USBDM_4_12_1_295_Win. When I try to write a working dump to the flash 56f8006, a windows 7 x64 write "close the program". When I use the software version USBDM_4_12_1_170_Win - all OK. Why? Help me please?
-
Arin Kudlacek posted a comment on discussion Help
I am running into an issue programming a NXP MKV42F64VLH16 with the USBDM flash programmer application. I modified arm_kinetis_devices.xml with the following: <device name="MKV42F64VLH16" family="CortexM4F" subfamily="MKV42F64"> <memoryref ref="kinetis_M4_16K_16K_Ram"> <memoryref ref="FTFA_PFlash0_SEC_64K_2KS"> <memoryref ref="kinetisIO_MK"> <sdid value="0x41601145" mask="0xFFF00F80"> <tclscriptref ref="Kinetis-MKxx-Scripts"> <flashprogramref ref="Kinetis-FTFA-MK-flash-program"> <registerdescriptionref...
-
Marcio Antonio Machado posted a comment on discussion Open Discussion
I need someone to create script to write dipsositive MC56F8335 in usbdm software 4.12.1.140, I can pay for the service. The file to be written is attached
-
-
-
-
-
Assumed fixed in V4_12_1_295
-
-
-
-
-
-
-
-
-
-
Liu Hong posted a comment on discussion Help
It works successfully! Thank you for your software! [cid:image001.png@01D87B67.82516550] From: discussion@usbdm.p.re.sourceforge.net discussion@usbdm.p.re.sourceforge.net On Behalf Of Peter O'Donoghue Sent: Saturday, June 4, 2022 13:32 To: [usbdm:discussion] 1237994@discussion.usbdm.p.re.sourceforge.net Subject: [usbdm:discussion] "Execution of TCL script returned an error" while erasing S12XE I update the TCL scripts and programmer to better handle the UF32 which has issues. Unfortunately I missed...
-
It works successfully, after replace this file! Thank you for your help!
-
I updated the TCL scripts and programmer to better handle the UF32 which has issues. Unfortunately I missed one of the TCL files. This will be fixed in the next release. Please test using the attached file and advise if there is still a problem. Replace file in /DeviceData/HCS12
-
I update the TCL scripts and programmer to better handle the UF32 which has issues. Unfortunately I missed one of the TCL files. This will be fixed in the next release. Please test the using the attached file and advise if there is still a problem. Replace file in /DeviceData/HCS12
-
Newest Version: USBDM_4_12_1_290_Win.msi failed to erase S12XET MCU. this process stop and post a message box: "Execution of TCL script returned an error". However, USBDM_4_12_1_270_Win.msi and USBDM_4_12_1_280b_Win.msi can be used to erase / program S12XE MCU. So it seems that a new bug was introduced. All test above was done in same hardware: Desktop Win11 Pro, S12XET256
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >
