Problems using serial booloader for MC56F8367

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problems using serial booloader for MC56F8367

Jump to solution
1,442 Views
alexk
Contributor I

I am trying to use the bootloader that came with the CodeWarrior for DSC56800E v8.3 package to have the DSC load an S-Record via the COM port and afterwards run it on a MC56F8367 DSC. I am using the serial bootloader that came from CodeWarrior_for_DSC56800E_v8.3\Stationery\Processor_Expert_Examples\Bootloaders\56F83xx\serial_bootloader, and I am using the CodeWarrior USBTAP to load in the bootloader. Then I try to load in an S-record via the COM port (using Tera Term hyperterminal), and the problems begin. (The S-records I’m trying to load in through the COM port work correctly if I try to load them with the USBTAP.) Up until a few days ago, I’d get error # 6 (flash programming error), but now it just says “Application started from address 0x0000”, waits a few seconds, then displays the bootloader’s “Waiting for application S-Record” message. (The change occurred when I downloaded first the out.x.S file and then the out.p.S file using the COM port, but I don’t see how that could have caused it.)

Using the View Memory/Save Range utility of the USBTAP,  I get confusing results:

ORIGINAL:

S0110000000050524F4752414D264441544196

S32500000000 5CE2000054E2C60254E2C60254E2C60254E2C60254E2C60254E2C60254E2C602 AA

S32500000020 54E2C60254E2C60254E2C60254E2C60254E2C60254E2C60254E2C60254E2C602 CA

S70500080000F2

 

READBACK:

S024000000004D656D6F72792044756D7020503A30783030303030302D307830303031303044

S32500000000 5CE2000054E2C60254E2C60254E2C60254E2C60254E2C60254E2C60254E2C602 AA

S32500000010 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF EA

S32500000020 54E2C60254E2C60254E2C60254E2C60254E2C60254E2C60254E2C60254E2C602 CA

S32500000030 FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFCA

S30700000100FFFFF9

S7050000008476

 

Each line originally has 64 data characters, or 32 bytes, but the addresses in the readback advance by 0x10, or 16 bytes, implying that there is simultaneously data written and empty space there? I’m pretty sure that’s not how it’s meant to be, but I don’t know if that’s a symptom of the real problem or just a side effect.

Anybody have any suggestions for me?


Thanks,

Alex

P.S. My CodeWarrior IDE version is 5.9.0, and I am using a Windows 7 computer. I downloaded a zip file with css updates to get the USB TAP to work.

Labels (1)
0 Kudos
1 Solution
1,113 Views
alexk
Contributor I

Ok, I've managed to solve my problem. The thing that was causing the issue described in my previous post was that I was using a byte addressing system instead of a 16-bit word addressing system. You can switch by going Settings->M56800E Linker and un-marking the "Generate Byte Addresses" checkbox. My other problems were solved by some changes to the linker file.

View solution in original post

0 Kudos
1 Reply
1,114 Views
alexk
Contributor I

Ok, I've managed to solve my problem. The thing that was causing the issue described in my previous post was that I was using a byte addressing system instead of a 16-bit word addressing system. You can switch by going Settings->M56800E Linker and un-marking the "Generate Byte Addresses" checkbox. My other problems were solved by some changes to the linker file.

0 Kudos