This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

MCP 3.10.0.14 + Windows 7 + MEFW 0.11.0 crashes

After installing the Master Control Panel 3.10.0.14 (x64) on Windows 7 Professional, uninstalling JLink V5.02a (which MCP really does not like) so it uses V4.98c, and realizing the firmware in the directory named pca10000 is actually relevant to pca10028/pca10031, I still can't get past this issue:

As soon as the device is inserted into USB and MCP connects to it, it crashes with these details:

Problem signature:
  Problem Event Name:	BEX
  Application Name:	MasterControlPanel.exe
  Application Version:	3.10.0.14
  Application Timestamp:	55d6e033
  Fault Module Name:	JLinkARM.dll_unloaded
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	55393847
  Exception Offset:	082fd7a3
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

The log shows the material below. Reproduced with MEFW_nrf51822_0.11.0_firmware_1M.hex flashed onto both a PCA10031 and a PCA10028 (with P30 jumper to ground).

2;22:48:54.8387 [MainThread] Master Control Panel 3.10.0.14
3;22:48:55.0387 [MainThread] Log verbosity level: High
4;22:48:55.1287 [MainThread] nrfjprog.dll 5.2.0.45231
5;22:48:55.1387 [MainThread] JLinkARM.dll 4.98c
6;22:48:55.1387 [MainThread] 681982376 - COM43
7;22:48:55.1487 [MainThread] nrfjprog.dll 5.2.0.45231
8;22:48:55.1587 [MainThread] HciJLinkDriver opened (COM43, 1000000-8-None-1-RequestToSend)
9;22:48:55.1587 [681982376][MainThread] JLinkARM.dll 4.98c
10;22:48:55.1687 [681982376][MainThread] 681982376 - COM43
11;22:48:56.1908 [681982376][MainThread] HCI command: BTLE_CMD_READ_BD_ADDR
12;22:48:56.1908 [681982376][MainThread] Serial port write: 01-09-10-00
13;22:48:56.1908 [681982376][MainThread] Waiting for event packet. Timeout is 500ms
14;22:48:56.2208 [681982376][ReadPacketQueueThread] Serial port read: 04-0E-0A-01-09-10-00-56-FF-99-00-CD-29
15;22:48:56.2508 [681982376][ReadPacketQueueThread] HCI event: BTLE_EVENT_COMMAND_COMPLETE, OpCode: BTLE_CMD_READ_BD_ADDR, Status: BTLE_STATUS_CODE_SUCCESS, BdAddress: 0x29CD0099FF56
16;22:48:56.2508 [681982376][MainThread] Finished waiting for event packet. PacketReceived:True
17;22:48:56.2508 [681982376][MainThread] HCI command: NRF_CMD_SET_BD_ADDR, Address: 0x9B-5A-F7-EE-A9-12
18;22:48:56.2608 [681982376][MainThread] Serial port write: 01-03-FC-06-9B-5A-F7-EE-A9-12
19;22:48:56.2608 [681982376][MainThread] Waiting for event packet. Timeout is 500ms
20;22:48:56.2608 [681982376][ReadPacketQueueThread] Serial port read: 04-0E-04-01-03-FC-00
21;22:48:56.2608 [681982376][ReadPacketQueueThread] HCI event: BTLE_EVENT_COMMAND_COMPLETE, OpCode: NRF_CMD_SET_BD_ADDR, Status: BTLE_STATUS_CODE_SUCCESS
22;22:48:56.2608 [681982376][MainThread] Finished waiting for event packet. PacketReceived:True
23;22:48:56.2608 [681982376][MainThread] HCI command: NRF_CMD_GET_VERSION_INFO
24;22:48:56.2608 [681982376][MainThread] Serial port write: 01-06-FC-00
25;22:48:56.2608 [681982376][MainThread] Waiting for event packet. Timeout is 500ms
26;22:48:56.2608 [681982376][ReadPacketQueueThread] Serial port read: 04-0E-2C-01-06-FC-00-6D-65-66-77-5F-6E-72-66-35-31-38-32-32-5F-30-2E-31-31-2E-30-2E-31-38-33-37-38-00-00-00-00-00-00-00-00-00-00-00-00-00-00
27;22:48:56.2608 [681982376][ReadPacketQueueThread] HCI event: BTLE_EVENT_COMMAND_COMPLETE, OpCode: NRF_CMD_GET_VERSION_INFO, Status: BTLE_STATUS_CODE_SUCCESS, VersionInfo: mefw_nrf51822_0.11.0.18378
28;22:48:56.2708 [681982376][MainThread] Finished waiting for event packet. PacketReceived:True

FWIW, if the device is absolutely blank it also crashes, after not receiving any response to BTLE_CMD_READ_BD_ADDR, so I had to get the MEFW firmware on the devices using nRFGo.

Any ideas?

Parents
  • If there are dump files I don't know where they are. They're not in the directory where the log is found.

    At this point I don't plan to spend more time on this: I'd hoped MCP be a quick way to gain insight into the examples and capture working packet traces while developing new central and peripheral services on my Linux systems for the nRF51 to use, but since it doesn't work for me I'll move directly to using noble.

Reply
  • If there are dump files I don't know where they are. They're not in the directory where the log is found.

    At this point I don't plan to spend more time on this: I'd hoped MCP be a quick way to gain insight into the examples and capture working packet traces while developing new central and peripheral services on my Linux systems for the nRF51 to use, but since it doesn't work for me I'll move directly to using noble.

Children
No Data
Related