D-Bug12 4.0.0b32 broken (BDM POD mode)

[imajeff]

Is D-Bug12 4.0.0b32 (BDM POD mode) broken? I can't do much with
Flash memory banks. I'm new to the DG128B but have trouble even with
my well-tested DP256.

- I think the major thing is that it did not seem to initialize Flash
in order to write to it. That makes it tedious to init every time it
gets reset!
- `asm` should be able to disassemble from Flash banks, but
keeps saying "Bad Extended Address".
- My S19 file won't load all the way with `fload` because dbug says
"S-Record Out Of Range" even the records are within PPAGE 3e and 3f.
- Why do docs conflict for 128K Flash banks? My docs say start PPAGE 0x00 but
new docs say 0x38. I still don't know which one.

----
Experimenting:

S>ver
4.0.0b32
S>device

Device: S12DB128, MC9S12DT128, MC9S12DG128, MC9S12DJ128, MC9S12DB128, MC9S12A 2
EEPROM: $0800 - $0FFF
Flash: $8000 - $BFFF Pages: 8 PPAGE at: $0030
RAM: $2000 - $3FFF
I/O Regs: $0000 - $03FF
Target Speed: 16000 KHz

S>asm 8000
PPAGE Value Required With Address
S>asm 00:8000
Bad Extended Address
S>asm 30:8000
Bad Extended Address
[*which is it? old docs say Flash starts at PP 00, new says 80]
S>bs 00:8000 07:bfff 35
Bad Extended Address

I made this S19 file "tst.s19":
S00B000062757A7A2E7331391E
S224018000CF4000180B390010180B000011180B080012164184CEC04ACD2000CC01FA2707D9
S804FF4000BC

S>fload
[*no errors displayed in minicom]
[*my larger S19 file showed error "S-Record Out Of Range" which I don't see]
S>upload 018000 01801f ;f
S224018000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF7A
S9030000FC
[*shows "tst.s19" not programmed]
S>pp 6

PP PC SP X Y D = A:B CCR = SXHI NZVC
06 0000 2000 0000 0000 00:00 1101 0000
xx:0000 00 BGND
S>md 8000

8000 FF FF FF FF - FF FF FF FF - FF FF FF FF - FF FF FF FF ................
[*should show bytes programmed from "tst.s19" above]
S>md 100

0100 00 FE 00 00 - FF C1 00 00 - 00 00 00 00 - 00 00 00 00 ................
[*is this showing that D-Bug12 did not initialize Flash registers?]

[KH_SRNL]

I'm having the exact same problem.  Technological Arts sells a BDM that runs D-Bug12.  The original modules I purchased contained D-Bug12 4.0.0B18.  This specific version of D-Bug worked great and I had no problems running it with the MC9S12C32 chip.  Later versions of the module were shipped with 4.0.0B32.  I've never had any success at getting these modules to run.  I received the same error messages (S Rec out of range).

Does anyone know where to download D-Bug12 4.0.0B18?  I, for one, would like to get a copy so I can get some of my newer debug modules running correctly.

[kef]

KH@SRNL, I haven't used D-Bug12, but like Imajeff noted, are your Srecords in linear (physical) format? That would mean all your C32 S records must be between F8000 and FFFFF.

Are you using Codewarrior? If yes, then you may find right *.phy (S records) file in your projects /bin folder.

[imajeff]

ooooh aaaaaai seeeee,

This was hard to solve because I was focusing on the presumption that PPAGE [00..07] was Flash as documented previous, but it is hex [38..3f] good, I like that better.

Originally I was asking why was all original documentation wrong... It looks like there was some S12 DP256 and HC912 DG128 side-by-side in D-Bug12 appendix (but no 9S12DG128 mentioned). I wonder how many times I've misread because they were sly enough to make different DG128 devices in two almost alike but different families. I guess Freescale was not thinking straight. I won't go into that again, though.

So the only reason I think that commands (fload, asm, bs) didn't work is because when I guessed the alternate PPAGE locations, I used 0x30 instead of 0x38 because I'm so used to DP256. Then I think I had a S19 format problem when I couldn't fload to the DP256. It was strange that as soon as I set FCLKDIV for the DP256 manually, everything else started working. But now I can do it without initializing that.

I have no clue why the BDM debugger can fload to Flash yet FCLKDIV on the target is still not initialized ?!

Well, all my problems had to do with knowing the right address ranges.
DG128B
PPAGE ranges [0x38..0x3f]
linear address range [0x0e0000..0x0fffff]

Thanks for all your help (well, at least if someone does add a comment)

Message Edited by imajeff on 2006-09-19 05:02 PM