[Efi332] BDM troubles

Sat Jul 2 17:56:12 UTC 2005

Humm... I think I'll try switching my board back to use the built-in interface. It would be nice to eliminate the "extra" cords, power, and hardware.

David - are you using the parallel cable that came with the Phytec kit, or a standard cable (I haven't tested the pins with a meter, but I seem to remember that the cable that comes with the Phytec kit is not a standard parallel cable)?
  ----- Original Message ----- 
  From: bowtievette at aol.com 
  To: efi332 at diy-efi.org 
  Sent: Saturday, July 02, 2005 11:58 AM
  Subject: Re: [Efi332] BDM troubles

  The BDM interface built into the Phytec development board is functionally identical to the wiggler interface, if not completely identical. You should be able to connect using either interface so thats probably not your problem. 

  One thing I found when investigating using gdb was that out of the box, it did not support a parallel interface to the BDM. It only supported the ethernet interface, so the only way I was able to get it to work was with Macraigor's OCDemon program which essentially echoes the ethernet port activity on the parallel port. Your gdb version may have parallel BDM support but thats something to verify.

  As a stopgap, you might try using Macraigor's OCD Commander as they have a linux version for it. Thats probably not a final solution for you though since it only allows assembly level debugging. But it would get you connected so that you can load software at least. David Eicher is using commander I think and can probably help out with initialization scripts and such.

  -----Original Message-----
  From: Paul Helmuth <PaulHelmuth at SprintMail.com>
  To: efi332 at diy-efi.org
  Sent: Sat, 2 Jul 2005 11:11:50 -0500
  Subject: Re: [Efi332] BDM troubles

  I suspect (mind you, I don't have much to go on here) that your problem is related to trying to use Phytec's "built-in" interface with anything other than the Codewarrior software that they ship with it. 

  Of course, it should be possible to use that connection, but I think things are a whole LOT "cleaner" switching to their external BDM header. At least there you have all of the pins documented. 

  I use a Macraigor Wiggler to supply the BDM-to-parallel port interface and as I mentioned in my previous email, there is a link on James' web page that gives some direction for matching the Macraigor outputs with the Phytec external BDM header. 

  The Macraigor unit has been 100% reliable for me. It's not the fastest interface, (they also have faster ones - just more $$$) but it's pretty inexpensive. 

  ----- Original Message ----- From: "Doug Brunner" <doug at udel.edu> 
  To: <efi332 at diy-efi.org> 
  Sent: Saturday, July 02, 2005 10:51 AM 
  Subject: Re: [Efi332] BDM troubles 

  > My problems have been with GDB's support for the BDM interface. I'm > actually using the Phytec board's internal BDM (parallel port on the > board) rather than the 10-pin header for an external BDM, since my only > BDM is a Tilbury unit from way back when that has been more than a little > flaky. 
  > 
  > As I understand it, GDB needs some kind of addon to talk to a BDM via the > parallel port. I've tried MPCBDM as discussed on James' 555 Webpage, > running gdb 5.0 (since that's the only version I've seen the patch for) as > root, and it doesn't seem to accomplish anything--it just hangs when I try > to connect to the board. What has everyone else been using? 
  > 
  > --Doug Brunner 
  > 
  > Paul Helmuth wrote: 
  > 
  >> I'm (reasonably) sure everyone that has done anything with the Phytec >> development board has used the JTAG/BDM port. 
  >> 
  >> Since you are using GDB, I assume that you are using the GCC tool chain. >> Since you are using that, I also assume that you are using the external >> BDM port. This means you have some BDM port interface (like a Wiggler). 
  >> 
  >> So - you need to make sure that all of your pin-outs match between your >> BDM interface and the Phytec BDM port. As an example, two of the pins are >> reversed between the Phytec port and my Macraigor Wiggler. I have a note >> on James' 555 web page about that switch. Also, you need to follow >> Phytec's bulletin on setting the development board jumpers for using the >> external BDM port. 
  >> 
  >> Other than that, everything should work - but I haven't used these tools >> with Linux. 
  >> 
  >> -Paul 
  >> 
  >> 
  >> ----- Original Message ----- From: "Doug Brunner" <doug at udel.edu> 
  >> To: <efi332 at diy-efi.org> 
  >> Sent: Friday, July 01, 2005 10:11 PM 
  >> Subject: [Efi332] BDM troubles 
  >> 
  >> 
  >>> I'm trying to start talking to my Phytec 555 board and having lots of >>> trouble. It's on the Phytec development board, so I'm using their BDM, >>> which I can't get GDB to interact with. I'm running all this under >>> Linux. 
  >>> 
  >>> What have the rest of you been using for BDM support? 
  >>> 
  >>> --Doug Brunner 
  >>> _______________________________________________ 
  >>> Efi332 mailing list 
  >>> Efi332 at diy-efi.org 
  >>> http://lists.diy-efi.org/mailman/listinfo/efi332 
  >>> 
  >> 
  >> _______________________________________________ 
  >> Efi332 mailing list 
  >> Efi332 at diy-efi.org 
  >> http://lists.diy-efi.org/mailman/listinfo/efi332 
  >> 
  > 
  > _______________________________________________ 
  > Efi332 mailing list 
  > Efi332 at diy-efi.org 
  > http://lists.diy-efi.org/mailman/listinfo/efi332 
  >  
  _______________________________________________ 
  Efi332 mailing list 
  Efi332 at diy-efi.org 
  http://lists.diy-efi.org/mailman/listinfo/efi332 

------------------------------------------------------------------------------

  _______________________________________________
  Efi332 mailing list
  Efi332 at diy-efi.org
  http://lists.diy-efi.org/mailman/listinfo/efi332
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.diy-efi.org/pipermail/efi332/attachments/20050702/53b2f53e/attachment.html 