TBDML + OSBDM ??

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

TBDML + OSBDM ??

6,600 Views
baddad
Contributor I
Does anyone know what it would take to create a version that would support both S08 and S12 devices?
 
I know the hardware can support them.  I don't see why the firmware could not be modified, but what about the DLL files? 
 
Would changes to the Codewarrior debugger have to be made to recognize the TBDML and OSBDM as one in the same?
 
Thanks,
BadDad
0 Kudos
Reply
5 Replies

564 Views
Nabla69
Contributor V
Hello,

Sorry I haven't been around much lately...

The hardware can do it and so does the debugger.
The issue is more in the different DLL that interface the debug cable with CodeWarrior.
You would need to rewrite the code of the JB16 for the OSBDM08 to be compatible with the DLL of the TBDML. Please note that there are slight differences between the two BDM and that is why one is not supporting the other.

Cheers,
Alban.
0 Kudos
Reply

564 Views
JimDon
Senior Contributor III
Of course, the JM code needs to be changed as well. The problem is the GDI dll for the OSBDM does not currently use TBDML.DLL or those entry points, so my point is you would write a replacement DLL that "talks" to the new code in the JM chip, but "looks Like" the old DLL.

The big question is where did  DanielM get off to?

He could probably figure out the details quickly....
0 Kudos
Reply

564 Views
gnzork
Contributor I
Hi
 
I'm interested in taking a JB16 debugger system that supports 08 parts and giving it support for s12 parts as well using Turbo BDM.  I know I need to alter the dlls.  Do you know where I can find the source to the dlls?
 
Thanks
0 Kudos
Reply

564 Views
pgo
Senior Contributor V
Dear Macias,

Not really worth doing - unless for interest :smileyhappy:

Please see this link:

Combined TBDML/OSBDM Code

bye


Message Edited by pgo on 2009-01-28 06:18 AM

Message Edited by pgo on 2009-01-28 06:20 AM
0 Kudos
Reply

564 Views
JimDon
Senior Contributor III
Well, TBDML.DLL and OPENSOURCEBDM.DLL have a different, but similar interfaces.
To make it so there are no changes to the debugger, I suppose you would have to make a new version
of OPENSOURCEBDM.DLL that talked to the TBDML instead.

As for the firrmware, download the source code for both fo thern, and see what it would take to merge the code.

_LibMain@12
_opensourcebdm_bdm_sts@4
_opensourcebdm_close@0
_opensourcebdm_dll_version@0
_opensourcebdm_get_last_sts@0
_opensourcebdm_get_speed@0
_opensourcebdm_get_version@0
_opensourcebdm_init@0
_opensourcebdm_mem_dlend@0
_opensourcebdm_mem_dlstart@0
_opensourcebdm_open@4
_opensourcebdm_read_bkpt@0
_opensourcebdm_read_block@12
_opensourcebdm_read_byte@4
_opensourcebdm_read_regs@4
_opensourcebdm_read_status@0
_opensourcebdm_set_speed@4
_opensourcebdm_set_target_type@4
_opensourcebdm_target_go@0
_opensourcebdm_target_halt@0
_opensourcebdm_target_readyfor_datald@0
_opensourcebdm_target_reset@4
_opensourcebdm_target_step@0
_opensourcebdm_target_sync@0
_opensourcebdm_write_bkpt@4
_opensourcebdm_write_block@12
_opensourcebdm_write_byte@8
_opensourcebdm_write_control@4
_opensourcebdm_write_reg_ccr@4
_opensourcebdm_write_reg_d@4
_opensourcebdm_write_reg_pc@4
_opensourcebdm_write_reg_sp@4
_opensourcebdm_write_reg_x@4



_LibMain@12
_tbdml_bdm_sts@4
_tbdml_close@0
_tbdml_dll_version@0
_tbdml_get_last_sts@0
_tbdml_get_speed@0
_tbdml_get_version@0
_tbdml_init@0
_tbdml_open@4
_tbdml_read_bd@4
_tbdml_read_block@12
_tbdml_read_byte@4
_tbdml_read_regs@4
_tbdml_read_word@4
_tbdml_set_speed@4
_tbdml_set_target_type@4
_tbdml_target_go@0
_tbdml_target_halt@0
_tbdml_target_reset@4
_tbdml_target_step@0
_tbdml_target_sync@0
_tbdml_write_bd@8
_tbdml_write_block@12
_tbdml_write_byte@8
_tbdml_write_reg_ccr@4
_tbdml_write_reg_d@4
_tbdml_write_reg_pc@4
_tbdml_write_reg_sp@4
_tbdml_write_reg_x@4
_tbdml_write_reg_y@4
_tbdml_write_word@8

0 Kudos
Reply