Can not detect the serial port number when Connect to the nordic 51822 using jlink in ubuntu 14.4

[desword]

As shown in title, I am using the ubuntu 14.04 in virtualbox. When I connect the Nordic 51822 development kit to my PC, I can only detect the serial number of this device, and I can not find the serial port number using 'dmesg | grep xx' like (devzone.nordicsemi.com/.../)

In expectation, I would get the following mesg:

kaspar@ubuntu:~/RIOT$ dmesg | grep 'cdc_acm.*USB ACM device' | tail
[25398.308837] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[26152.729879] cdc_acm 1-1:1.0: ttyACM0: USB ACM device

However, I only get following mesg without the filter of grep:

[  785.440538] usb 1-2: new full-speed USB device number 3 using ohci-pci
[  785.641516] usb 1-2: New USB device found, idVendor=1366, idProduct=0101
[  785.641519] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  785.641520] usb 1-2: Product: J-Link
[  785.641521] usb 1-2: Manufacturer: SEGGER
[  785.641522] usb 1-2: SerialNumber: 000000123456

So, how to fix this problem? without the serial port I can not just flash the hello-world example!

serial.serialutil.SerialException: could not open port 000000123456: [Errno 2] No such file or directory: '000000123456'

[Stian Røed Hafskjold]

If you hold down the reset button while turning on the kit, does it show up as a mass storage USB device called BOOTLOADER? And do you get the New USB device found, idVendor=0d28, idProduct=0204 from dmesg?

[Stian Røed Hafskjold]

And is the serial number really 000000123456? Or did you just change it before posting?

[desword]

Thanks! I just do the things as you said, but I can not see the idVendor or idProduct change. it is still idVendor=1366, idProduct=0101. I didn't change the serial number and it is "000000123456" when I plugin.

[desword]

Maybe the reset button is broken?

[Stian Røed Hafskjold]

Where did you buy the PCA10028? Are you sure you have the official Nordic one and not a copy? The serial should not be 123456 and it seems like the wrong Segger firmware is loaded to the device. Is there an Atmel ATSAM3U2C chip on the board?