CW 10.1 Debug - Unable to write Flash (USB TAP)

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

CW 10.1 Debug - Unable to write Flash (USB TAP)

1,638件の閲覧回数
Kafre
Contributor III

Hello all,

 

I use Codewarrior 10 for MCU with MQX 3.6.2 and I'm flashing a M54452 Coldfire V4 MCU using USB TAP.

 

I'm currently trying to flash my MCU with no success. Every time I try to debug I get a signal halt exception: No source avaliable for 0x8000040A (that is indeed the MCU's SRAM direction). When I check that memory space using the Memory Browser, I see something loaded. I suppose that it is the internal program to load the FLASH and the SDRAM. The dissasembly shell points to the "rte" instruction, by the way.

 

If I try to read the content of the Flash using Memory Browser I get a buch of Fs. When reading the SDRAM I get 0s.  This means that both are empty but I don't get any error in the launching process and my .S19 and .XMAP files seem correct.

 

Anybody has a clue of what could I be doing wrong?

 

Thanks.

ラベル(1)
タグ(1)
0 件の賞賛
返信
3 返答(返信)

1,179件の閲覧回数
Kafre
Contributor III

Hello again,

 

I'm triying to run my program using a direct aproach (launching directly the ttf task). I get this code: 

 

 

fl::target -lc "Flash_Debug"fl::target -b 0x80000000 0x8000fl::target -v on -l off -ie on -i "D:/workspace/LIBS/CCU.cw10/mqx/dbg/mcf54452.cfg" -p MCF54452cmdwin::fl::device -d "S29GL256N" -o "16Mx16x1" -a 0x0 0x1ffffffcmdwin::fl::image -f "D:\\workspace\\Shell_test\\CCU_Flash_Image_Debug\\Shell_test_Flash_d.elf" -t "Auto Detect" -re off -oe offcmdwin::fl::erase image Beginning Operation ...    ------------------------- Auto-detection is successful.     File is of type Elf Format.    Initializing remote connection ...    Performing target initialization ...     Downloading Flash Device Driver ...    Reading flash ID ...Erasing Sector 0x00000000 to 0x0001FFFF ...    Erasing Sector 0x00020000 to 0x0003FFFF ...     Erasing ... Erase Command Succeeded    cmdwin::fl::write Beginning Operation ...    ------------------------- Programming file D:\workspace\Shell_test\CCU_Flash_Image_Debug\Shell_test_Flash_d.elf   Auto-detection is successful.     File is of type Elf Format.     Downloading Flash Device Driver ...    Reading flash ID ...Auto-detection is successful.     File is of type Elf Format.    Downloading 0x00006800 bytes to be programmed at 0x00000000    Programming ..............................................................  Programming ..............................................................  Programming ..............................................................  Programming ..............................................................  Programming ..............................................................  Programming ..............................................................

 

 

And goes on and on. It never stops programming!

 

Any idea?

 

Cheers,

0 件の賞賛
返信

1,179件の閲覧回数
Kafre
Contributor III

This is what I get when I tipe "show cc" in the CW Connection Server:

 

 

(bin) 6 % show ccReceived  CMD_CC_VERSIONAvailable USB TAPs: 08160104Opening connection to USB TAP 081601040: USB TAP (JTAG) (utap:) Loader software ver. {1.9}Sending code to USB TAP - please waitSending CMD_SERVER_ALIVESending CMD_SERVER_ALIVESending CMD_SERVER_ALIVEAvailable USB TAPs: 08160104Opening connection to USB TAP 08160104Received  CMD_HTI_SET_CRC32USB TAP command done - OkUSB TAP command done - Ok0: USB TAP (JTAG) (utap:) CC software ver. {1.3}

 

 

0 件の賞賛
返信

1,179件の閲覧回数
Kafre
Contributor III

Hello again,

 

My Flash was wrongly connected. I connected the Address 0 pin for a 16 bits addressable memory and as commented on the FAQ that will not work. 

 

I'm making a workaround using the Flash Tool Kit since I can't physically change the pin connection. I will create a new topic here about the FTK if I find it necessary.

 

Thank you very much. 

0 件の賞賛
返信