Jump to content
Sign in to follow this  
H2SO4_on_PIC

Why cannot debug PIC12F675?

Recommended Posts

Guest Dave

H2SO4,

 

You don't need to wait!

The PIC12F675 contains a PIC16 core, so you should be able to edit an existing TDF file (Target Descriptor File) and change it to match this device.

 

Also you will need to add an entry in the MAP.TXT file for the new device.

 

Good Luck.

 

Regards

Dave

:)

Share this post


Link to post
Share on other sites

OK, I did what you suggested -- but the GUI still returns:

 

Can't read configuration of the target processor 'PIC12F629'

 

This SourceBoost IDE version supports debugging of only 16 PIC series of microprocessors

and contains descriptions of only a few supported PIC types. If you are trying

to debug PIC16 target and this target is missing you can either wait for the next

SourceBoost IDE release which may contain the missing processor description file or

create your own target description file (.TDF). Please read the TDF.doc file

that is in the 'config' compiler subdirectory for more information.

 

So, where is the problem?  Thanks.

Share this post


Link to post
Share on other sites

Hmm.

Copied PIC16F628.tdf into PIC12F629.tdf.  Added entry to map.txt for PIC12F629.  This now works.

 

However, when I edited the PIC12F629 to now reflect the GPIO port, instead of PORTA or PORTB, I now get the error message.  What's going on?  I can email you my 'new' PIC12F629.tdf, if it will help.

Share this post


Link to post
Share on other sites
Guest Dave

AllanL5,

 

The simulator was written for and tested with PIC16 targets. Some of the PIC12's have a PIC16 core, but there are some differences - I/O port naming for one. So there are no gurantees that this will work, but currently I see now reason why it should not.

 

Please mail me the TDF file.

 

Regards

Dave

Share this post


Link to post
Share on other sites

File is sent.

 

It occurs to me that I could continue to call the GPIO port (unique to the 12F629) PORTB -- just changing the addresses in the TDF file -- and this might keep the simulator happy enough, and allow continued use of all those nice Peripherals that want to be connected to PORTA or PORTB or...

 

Perhaps Dave can figure out where I messed up the 12F629 TDF file -- OR, we need to keep the PORTB entity in it.

Share this post


Link to post
Share on other sites

Join the conversation

You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...