medbg tool not showing up

Go To Last Post
5 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello wonderful people, 

 

I am getting back to embedded programming after a break, so appreciate the patience with this noob issue. I bought some AtTmega-328P-XMINI xplained boards and am trying to program them using AS 7.0 on Win 10.1 machine. The first time I connected the board, Windows installed the driver with the device manager listing the device as a 'mEDBG Virtual COM Port'. I launched AS 7.0 and created a new project with ATmega328P as the target device. However, I dont see medbg listed under tools as shown in the image below"

 

I looked around this forum and found the post where manually changing the driver to 'USB Input device' was recommended for this issue. I tried that approach to no avail. I also changed the device to ATmega328PB based on another forum post on the topic with the same result. I tried ATMEL Start, which only lists ATmega328PB xplained mini as a target device, to ensure my environment is automatically setup, but alas no change. 

 

On a serial monitor I can see that device is converting button presses to morse code - which indicates this is not a driver issue, rather something on AS end. Interestingly, I can use serial monitor regardless of driver selection (virtual com vs usb input device).

 

This is the board I am working with:  https://www.microchip.com/DevelopmentTools/ProductDetails/PartNO/ATMEGA328P-XMINI

 

I am sure there something simple I am missing. Can you folks suggest some things I can try to get started?

 

Thanks in advance. 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Welcome to AVRFreaks!

 

I noticed in the pic you posted the Select debugger/programmer is blank, does that need to be selected first?

 

Jim

 

 

 

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Jim,

 

That's the dialog he's showing and if the mEDG has been detected it should be in that drop list beneath "Simulator". The fact that only "simulator" is listed there is the problem.

 

BTW:

rahilj wrote:
'mEDBG Virtual COM Port'
The vcom is not the debug channel - the debug chip on the board should appear as more than one USB class device. The Vcom is for comms but the debugging is on a different class. What does USBdview.exe show?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

My mEDBG (416 xplained nano) doesn't show up in Atmel Studio either but it does appear in MP LAB X IDE.  Might be worth giving that a shot?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,

 

Thanks for the help. I 'repaired' the AS installation and that seemed to do the trick. All my xplained kits pop up in AS as soon as I plug them in. I can also select mEDBG as a tool to program and debug. 

Must have been a fluke driver issue, but it had me pulling my hair all day yesterday!