Ubuntu in Virutalbox debug

[dimitrissideris]

Hi there,

I am using Lpcxpresso IDE v8.2.0 for 32bit ubuntu version inside virtualbox. I use it to debug an LpcXpresso 4367 board.

When i start debugging 1 emulator is found with name LPC-LINK2 CMSIS-DAP v5.173.

After that, Jtag configuration pops that 0 available JTAG devices are detected. Connect a device and try again.

Any ideas?

[lpcxpresso_supp]

Please take a step back and explain in detail what exactly the problem you are now reporting in this thread is?

Please also confirm that you followed the steps given in our previous post.

And please ensure that you clarify what OS is being run on your computer, and what OS within your virtual machine.

Regards,

LPCXpresso Support

[dimitrissideris]

The problem was that i could not debug from virtualbox.

My host OS is windows 10 and guest OS ubuntu 64bit.

I tried vmware player and managed to enter debug mode.

But the problem that remains is that debug out messages are not displayed in serial console.

This problem propably has to do with the debugout problem https://community.nxp.com/message/831322?commentID=831322&et=watches.email.thread#comment-831322 

no matter what virtualization tools.

So i consider this subject closed.

To debug lpcxpresso 4367 virtualbox didn't work and vmware worked.

[lpcxpresso_supp]

Our experience of using Virtualbox was that its USB support was not good enough to use for reliable debug probe connections.  This was sometime ago though - so the VirtualBox's USB support may have improved recently. Note that many of the LPCXpresso team do use Parallels or VMware Fusions on Macs to run LPCXpresso IDE on Windows and Linux quite successfully, including for debug. 

Anyway, the first thing to check would be that Windows has no grabbed control of the USB devices back from VirtualBox (which can happen in VM setups, particularly when the probe is soft-booted).

If that doesn't help, then I would suggest that you :

1) Power your board down

2) Delete any .launch files within your project

3) Delete any .swd or .jtag files within your project (probably in the Debug/Release folders)

4) Check that there are no debug related tasks still running (redlinkserv, arm-none-eabi_gdb*, crt_emu_*)

then power your board  up again and see if debugging now works.

It might also be worth trying with/without a powered hub.

Other things to try would be preprogramming the probe firmware with LPCScrypt, or manually soft-booting the probe - so that you can confirm what VirtualBox does with the probe before you start a debug session.

Booting LPC-Link2 

LPC-Link2 Debug Probe firmware programming 

However at the end of the day we cannot make any guarantees about debugging under VMs - USB can just be too temperamental (particular in our historic experience of VirtualBox).

Regards,

LPCXpresso Support.

[dimitrissideris]

I am using windows 10.

So im gonna try vmware player with ubuntu and see if it works.

[dimitrissideris]

Nope. The exact same thing happens with vmware player.

[dimitrissideris]

Debug worked in vmware player.

The thing is that i cannot see debug out messages printed to serial console which is why i had to install lpcxpersso ide inside a virtual machine.

(Native ide windows installation does not print debug out messages so i thought that inside a virtual machine would be a workaround)