u-blox C027 Update CMSIS-DAP Interface Firmware

C027 Firmware LPC1768 LPC11U35

To check your firmware version, open the MBED.HTM file on your mbed Microcontroller.

These instructions explain how to upgrade your firmware.

Data loss warning

Firmware updates may format the mbed Microcontroller drive. The current installed firmware will be erased.

/media/uploads/ublox/mbed_if_update.png

1. Get the CMSIS-DAP interface firmware

Download the latest firmware

It is not recommended to load any of the older versions:

2. Boot in the CRP DISABLD mode

Short the two test points while connecting the USB cable. A removable disk drive should appear.

3. Programm the Interface firmware

Delete the firmware.bin file that is stored on the disk. Copy the latest firmware to the disk.

4. Reboot the Interface

Reboot the the interface by disconnecting and reconnecting the USB cable. This time make sure that the test-points are no longer shorted.

5. Verify

The usual Mbed disk appears. Open the MBED.HTM file. This should bring you to the C027 Platforms Page Remark: The html file contains the build date as a html comment.

6. Finished!


Report

21 comments on u-blox C027 Update CMSIS-DAP Interface Firmware:

14 Feb 2014

Hi Ublox,

  1. Shorted out pins and pluged in USB, device starts up as CRP Disabled.
  2. Deleted the firmware.bin.
  3. Copied the file lpc11u35_lpc1768_if_mbed_2014feb06.if to the drive.
  4. Removed the USB cable. Power down the device.
  5. Pluged in the USB cable.

Now the device refuses to attach as a USB device.

Is there anything else I need to do to get my device two work? I now have to bricks!!!

Kind regards, Nicholas

14 Feb 2014
14 Feb 2014

Hi Sam,

thanks for the link! :-)

Quick question. I've noticed that your binary files are ending in "mbed_if.bin". The link for the new binarys for the Ublox c027 end in only the ".if".

Does this file get converted on the embedded device to a binary executable ".bin" ? Or do I need to extract or add the ".bin" on the downloaded file?

Thanks for your help. And thanks for the link.

Kind regards, Nicholas.

14 Feb 2014

Tried just as ".if".

All good, managed to flash both Ublox devices. I've also managed to find the other problem.

Turns out to be a problem with the USB 3.0 Port on my Asus UX32A and the Linux Kernel I'm using.

Thanks for your help.

Kind regards, Nicholas.

28 Feb 2014

The if and bin files are the same fromat. They are just renamed to avoid accidental programming on a mbed drive instead of the CRP_DISABLED drive. The mbed drive does not accept if files.

24 Mar 2014

Hi mbed and ublox guys,

just to let you know I've been testing out the new version of firmware on the C027.

The platform now seems stable using Linux on a USB 2.0 port. Which is great news. :-)

I've just run some tests on my Asus Zenbook UX32 which has 3 x USB 3.0 ports. Currently dmesg shows many errors and debug when trying to get it working. What seems to be the best way to get drag and drop to work is to plug in the USB port first to the computer and only then inserting the power lead. However you are still unable to see printf statements across the USB interface with tools like screen or cutecom.

Debug I see:

debug seen on USB 3.0 port with C027 and the new c027 interface chip binary

[ 2424.855331] usb 3-1: new full-speed USB device number 16 using xhci_hcd
[ 2424.855349] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2425.078754] scsi10 : usb-storage 3-1:1.0
[ 2425.079171] cdc_acm 3-1:1.1: ttyACM0: USB ACM device
[ 2425.082035] generic-usb 0003:0D28:0204.0005: hiddev0,hidraw1: USB HID v1.00 Device [MBED MBED CMSIS-DAP] on usb-0000:00:14.0-1/input3
[ 2426.074257] scsi 10:0:0:0: Direct-Access     MBED     microcontroller  1.0  PQ: 0 ANSI: 2
[ 2426.074592] sd 10:0:0:0: Attached scsi generic sg3 type 0
......cut here......
[ 2426.089741] sd 10:0:0:0: [sdd] Attached SCSI removable disk
[ 2615.569107] usb 3-1: USB disconnect, device number 16
[ 2616.707041] usb 3-1: new full-speed USB device number 17 using xhci_hcd
[ 2616.707057] xhci_hcd 0000:00:14.0: ERROR: unexpected command completion code 0x0.
[ 2616.927828] usb 3-1: config index 0 descriptor too short (expected 122, got 9)
[ 2616.927839] usb 3-1: config 1 has 0 interfaces, different from the descriptor's value: 4

Kind regards, Nicholas

24 Mar 2014

And from my previous post .....

Once I'm in this state if I remove, hit reset and then re-insert the USB connector to the C027 i see this debug:

debug from second usb insertion

[ 4657.677817] ------------[ cut here ]------------
[ 4657.677831] WARNING: at /home/apw/COD/linux/drivers/usb/host/xhci.c:3500 xhci_address_device+0x2ad/0x2d0()
[ 4657.677837] Hardware name: UX32A
[ 4657.677840] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat cdc_acm usb_storage bnep rfcomm parport_pc ppdev binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek joydev arc4 snd_hda_intel snd_hda_codec uvcvideo coretemp snd_hwdep videobuf2_core snd_pcm videodev ghash_clmulni_intel asus_wmi rts5139(C) snd_seq_midi videobuf2_vmalloc snd_rawmidi sparse_keymap videobuf2_memops snd_seq_midi_event snd_seq aesni_intel cryptd snd_timer snd_seq_device aes_x86_64 iwlwifi mac80211 microcode btusb snd psmouse bluetooth cfg80211 serio_raw mei(C) soundcore snd_page_alloc mac_hid lp parport usbhid hid wmi i915 drm_kms_helper drm i2c_algo_bit video
[ 4657.677905] Pid: 30, comm: khubd Tainted: G        WC   3.4.0-030400-generic #201205210521
[ 4657.677906] Call Trace:
[ 4657.677909]  [<ffffffff81052cff>] warn_slowpath_common+0x7f/0xc0
[ 4657.677911]  [<ffffffff810627c0>] ? lock_timer_base+0x70/0x70
[ 4657.677914]  [<ffffffff81052d5a>] warn_slowpath_null+0x1a/0x20
[ 4657.677916]  [<ffffffff814da58d>] xhci_address_device+0x2ad/0x2d0
[ 4657.677918]  [<ffffffff814aec92>] hub_port_init+0x3c2/0x7a0
[ 4657.677920]  [<ffffffff8141b425>] ? update_autosuspend+0x45/0x90
[ 4657.677922]  [<ffffffff8141b55d>] ? pm_runtime_set_autosuspend_delay+0x5d/0x80
[ 4657.677925]  [<ffffffff814b07bf>] hub_port_connect_change+0x2af/0x9b0
[ 4657.677927]  [<ffffffff814b137a>] hub_events+0x38a/0x630
[ 4657.677929]  [<ffffffff8166b3e1>] ? __schedule+0x3f1/0x710
[ 4657.677931]  [<ffffffff814b1676>] hub_thread+0x56/0x1d0
[ 4657.677934]  [<ffffffff81076960>] ? wake_up_bit+0x40/0x40
[ 4657.677935]  [<ffffffff814b1620>] ? hub_events+0x630/0x630
[ 4657.677938]  [<ffffffff810763ee>] kthread+0x9e/0xb0
[ 4657.677940]  [<ffffffff81676164>] kernel_thread_helper+0x4/0x10
[ 4657.677942]  [<ffffffff81076350>] ? kthread_freezable_should_stop+0x70/0x70
[ 4657.677944]  [<ffffffff81676160>] ? gs_change+0x13/0x13
[ 4657.677945] ---[ end trace 37c69ad38afb48d7 ]---
[ 4657.677947] xhci_hcd 0000:00:14.0: Virt dev invalid for slot_id 0x3!
[ 4657.881562] usb 3-1: device not accepting address 21, error -22
[ 4657.881584] xHCI xhci_free_dev called with unaddressed device
[ 4657.881593] hub 3-0:1.0: unable to enumerate USB device on port 1
17 Apr 2014

Guys, i followed the description above to get the device into CRP DISABLD mode and updated with CMSIS DAP Firmware 2.01 (28 Feb 2014) and it's now bricked - there are no syslog messages when i plug the device in. more fun, it wont go back into CRP DISABLD mode. Does any one please have any suggestions to this problem

I'm using debian, kernel 2.6.32-5-686, USB2 port, with power supply 15V 1A

thanks and with best regard

-m

24 Apr 2014

Hello, I managed to successfully update to the latest firmware but unfortunately the device does not mount as MBED anymore. I had to revert to CMSIS DAP Firmware 2.01 (28 Feb 2014) which allows me to put binaries to the MBED but the fail.txt indicates TARGET NOT POWERED. Of course I have a 15 volt power supply well above 1500mA connected all the time.

Furthermore a multimeter indicates 0 volts at the 5v output of the board and a few mVolts at the 3.3V pin. It seems that there might be a big problem here..

I am using a Mac and I also have tried with a windows XP machine.

I would appreciate any ideas

Thanks!

03 Oct 2014

Tried to update to 2.01 of 23/04/14 but the MBED drive does not show anymore (MAC or Win7). I had to fallback on 2.01 of Feb 2014 to get access to MBED again

21 Nov 2014

Dears,

I'm getting "TARGET NOT POWER" fail text when trying to run a bin on the board after updating FW to 28 Feb 2014 file. I'm using a C027 dev board SARA G350 based, so is the FW released compatible between C027 based on (Lisa and) Sara too?

Thanks

Federico

11 Jan 2015

Hi, don't know if this is relevant to this subject. I have some trouble with the firmware on MAC OS X 10.9. With 2.01 I'm able to upload the application to the MBED drive with lpc11U35_lpc1768_if_mbed2014feb06.if, but the serial connection is not operating with the screen command in terminal. With the latest firmware version lpc11U35_lpc1768_if_mbed2014apr23.if the serial communication works but loading a .bin onto the MBED drive crashes and result to an error. What can I do to make it work? PS the serial and flash loading does work on a windows system.

With many thanks, Matthias

20 Jan 2015

Hello, I've managed to boot up in CRP DISABLD, and I'm able to delete and copy new firmware files to the device (Ublox C027). But when I then reboot (without the testpoints shorted) it still boots up in CRP DISABLD. I've tried all the versions of the firmware and tried without +7v power supply as well. Nothing helps.

Have anyone experienced this (and hopefully gotten well out of it)?

Many thanks Sebastian

20 Oct 2016

Hello, Thanks for giving useful information. After follow step 1-5 , i have updated my firmware.

04 Nov 2016

good afternoon. someone found the solution to the problem of CRP Disabld?

08 May 2017

Thanks guys, this fixes the Windows10 USB problem as well ( where the MBED disk keeps resetting every minute)

21 Apr 2018

Nicholas Herriot wrote:

Hi Ublox,

  1. Shorted out pins and pluged in USB, device starts up as CRP Disabled.
  2. Deleted the firmware.bin.
  3. Copied the file lpc11u35_lpc1768_if_mbed_2014feb06.if to the drive.
  4. Removed the USB cable. Power down the device.
  5. Pluged in the USB cable.

Now the device refuses to attach as a USB device.

Is there anything else I need to do to get my device two work? I now have to bricks!!!

Kind regards, Nicholas

The missing point in the instructions is that after you copy the .if image to the CRP DISABled drive and remove the USB cable to reboot, you need to press the reset button on the board. Afterward, the DAPLINK drive and COM port will appear again.

30 Apr 2018

Hi

I am trying download firmware 2,43 from provided link on top of this website but none of this links currently works. Can you advise?

Tkank you Remi

10 Aug 2018

Hello, after flashing firmware Ubuntu 18.04 mounts CRP DISABLD drive. I made update as described and have tried all firmwares but without luck at all. How to unbrick my ublox board?

28 Aug 2018

I followed the instructions to update the firmware to 2.43, additionally saving the old firmware file, but when I try to copy either image to the C027 I get an error saying "Not enough disk space to copy" My Ublox is now dead. Please help ASAP.

Note: problem may be that I'm using a Mac, and deleting from the Mac Finder may not delete the firmware.bin file. I tried deleting the file using the Terminal program, but when I try to copy the updated firmware I get an error (code -8084). I can't reboot the unit back into MBED after disconnecting and resetting.

Update: following my own advice, I also copied the firmware update to the C027 using Terminal rather than Finder. Finally working.

Steps I followed: 1. Find the path to the new firmware file on your Mac (e.g. = Macintosh HD/Users/<usr>/Downloads/ublox_c027_0243.if) 2. In Terminal, use "df" to list mounted volumes. Look for /Volumes/CRP DISABLD 3. "cd /Volumes/CRP\ DISABLD" 4. "rm firmware.bin" 5 . "cp <path to new firmware> ublox_c027_0243.if" 6. Unplug USB 7. Press reset button. 8. Restore USB 9. Mounted drive used to be MBED, now it appears as DAPLINK, but firmware is updated.

04 Apr 2019

Hello, The MBED drive is no longer displayed. I tried the update of firmware 2.43, but it is displayed when there is not enough file space. I try it at the terminal, but it is the same. Please tell me a good way.

p.s. I have also updated the Firmware! :-) On Mac, it is better to use the "dd" command instead of the "cp" command at the terminal.

Please log in to post comments.