CrossChasm Quick-Start guide firmware flashing to C5

145 views
Skip to first unread message

Kyle Kelly

unread,
Nov 17, 2016, 3:50:40 PM11/17/16
to OpenXC

I'm walking through the steps for Mac/Linux and when I get to Step 8 the following occurs:

$ avrdude -U flash:w:vi-firmware-type9-CROSSCHASM_C5-ctv6.0.3-csv6.0-1-gb3f9b6b.hex -c stk500 -p 32MX795F512L -C avrdude.conf -P 0x10000af7

avrdude: AVR Part "32MX795F512L" not found.


Valid parts are:

  t10  = ATtiny10        [avrdude.conf:15237]

  t8   = ATtiny9         [avrdude.conf:15197]

  t5   = ATtiny5         [avrdude.conf:15157]

  t4   = ATtiny4         [avrdude.conf:15117]

  ucr2 = 32UC3A0512      [avrdude.conf:15096]

  x128a4 = ATXMEGA128A4    [avrdude.conf:14998]

  x64a4 = ATXMEGA64A4     [avrdude.conf:14901]

  x32a4 = ATXMEGA32A4     [avrdude.conf:14804]

  x16a4 = ATXMEGA16A4     [avrdude.conf:14707]

  x256a3b = ATXMEGA256A3B   [avrdude.conf:14610]

  x256a3 = ATXMEGA256A3    [avrdude.conf:14513]

  x192a3 = ATXMEGA192A3    [avrdude.conf:14416]

  x128a3 = ATXMEGA128A3    [avrdude.conf:14319]

  x64a3 = ATXMEGA64A3     [avrdude.conf:14222]

  x256a1 = ATXMEGA256A1    [avrdude.conf:14125]

  x192a1 = ATXMEGA192A1    [avrdude.conf:14028]

  x128a1d = ATXMEGA128A1REVD [avrdude.conf:13931]

  x128a1 = ATXMEGA128A1    [avrdude.conf:13834]

  x64a1 = ATXMEGA64A1     [avrdude.conf:13737]

  m6450 = ATMEGA6450      [avrdude.conf:13548]

  m3250 = ATMEGA3250      [avrdude.conf:13359]

  m645 = ATMEGA645       [avrdude.conf:13170]

  m325 = ATMEGA325       [avrdude.conf:12981]

  usb82 = AT90USB82       [avrdude.conf:12801]

  usb162 = AT90USB162      [avrdude.conf:12617]

  usb1287 = AT90USB1287     [avrdude.conf:12428]

  usb1286 = AT90USB1286     [avrdude.conf:12239]

  usb647 = AT90USB647      [avrdude.conf:12051]

  usb646 = AT90USB646      [avrdude.conf:11862]

  m32u4 = ATmega32U4      [avrdude.conf:11674]

  t84  = ATtiny84        [avrdude.conf:11491]

  t44  = ATtiny44        [avrdude.conf:11309]

  t24  = ATtiny24        [avrdude.conf:11127]

  m128rfa1 = ATMEGA128RFA1   [avrdude.conf:10939]

  m2561 = ATMEGA2561      [avrdude.conf:10745]

  m2560 = ATMEGA2560      [avrdude.conf:10552]

  m1281 = ATMEGA1281      [avrdude.conf:10364]

  m1280 = ATMEGA1280      [avrdude.conf:10175]

  m640 = ATMEGA640       [avrdude.conf:9987]

  t85  = ATtiny85        [avrdude.conf:9806]

  t45  = ATtiny45        [avrdude.conf:9627]

  t25  = ATtiny25        [avrdude.conf:9447]

  pwm3b = AT90PWM3B       [avrdude.conf:9266]

  pwm2b = AT90PWM2B       [avrdude.conf:9083]

  pwm3 = AT90PWM3        [avrdude.conf:8900]

  pwm2 = AT90PWM2        [avrdude.conf:8716]

  t2313 = ATtiny2313      [avrdude.conf:8529]

  m328p = ATMEGA328P      [avrdude.conf:8341]

  t88  = attiny88        [avrdude.conf:8155]

  m168 = ATMEGA168       [avrdude.conf:7967]

  m88  = ATMEGA88        [avrdude.conf:7781]

  m48  = ATMEGA48        [avrdude.conf:7594]

  t861 = ATTINY861       [avrdude.conf:7406]

  t461 = ATTINY461       [avrdude.conf:7217]

  t261 = ATTINY261       [avrdude.conf:7028]

  t26  = ATTINY26        [avrdude.conf:6871]

  m8535 = ATMEGA8535      [avrdude.conf:6713]

  m8515 = ATMEGA8515      [avrdude.conf:6555]

  m8   = ATMEGA8         [avrdude.conf:6394]

  m161 = ATMEGA161       [avrdude.conf:6254]

  m32  = ATMEGA32        [avrdude.conf:6079]

  m6490 = ATMEGA6490      [avrdude.conf:5886]

  m649 = ATMEGA649       [avrdude.conf:5701]

  m3290p = ATMEGA3290P     [avrdude.conf:5518]

  m3290 = ATMEGA3290      [avrdude.conf:5333]

  m329p = ATMEGA329P      [avrdude.conf:5148]

  m329 = ATMEGA329       [avrdude.conf:4964]

  m169 = ATMEGA169       [avrdude.conf:4784]

  m163 = ATMEGA163       [avrdude.conf:4626]

  m162 = ATMEGA162       [avrdude.conf:4430]

  m1284p = ATMEGA1284P     [avrdude.conf:4240]

  m644p = ATMEGA644P      [avrdude.conf:4048]

  m644 = ATMEGA644       [avrdude.conf:3858]

  m324p = ATMEGA324P      [avrdude.conf:3667]

  m164p = ATMEGA164P      [avrdude.conf:3476]

  m16  = ATMEGA16        [avrdude.conf:3298]

  c32  = AT90CAN32       [avrdude.conf:3107]

  c64  = AT90CAN64       [avrdude.conf:2917]

  c128 = AT90CAN128      [avrdude.conf:2727]

  m128 = ATMEGA128       [avrdude.conf:2549]

  m64  = ATMEGA64        [avrdude.conf:2368]

  m103 = ATMEGA103       [avrdude.conf:2228]

  8535 = AT90S8535       [avrdude.conf:2107]

  8515 = AT90S8515       [avrdude.conf:1993]

  4434 = AT90S4434       [avrdude.conf:1910]

  4433 = AT90S4433       [avrdude.conf:1786]

  2343 = AT90S2343       [avrdude.conf:1662]

  2333 = AT90S2333       [avrdude.conf:1534]

  2313 = AT90S2313       [avrdude.conf:1421]

  4414 = AT90S4414       [avrdude.conf:1308]

  1200 = AT90S1200       [avrdude.conf:1193]

  t15  = ATtiny15        [avrdude.conf:1060]

  t13  = ATtiny13        [avrdude.conf:887]

  t12  = ATtiny12        [avrdude.conf:754]

  t11  = ATtiny11        [avrdude.conf:690]



I've either done something wrong (very likely) or something has changed regarding the part number. Can someone tell me the part number for this device? I didn't see anything on the OpenXC VI page. Thanks.

Kyle

Dominic Meroux

unread,
Nov 18, 2016, 2:14:47 PM11/18/16
to OpenXC
Hi Kyle, 

I may be on the wrong track here, but have you tried running "ls /dev/tty.usb*" when in the directory (while the C5 is connected to your computer via USB)? When I do this I get some output like "/dev/tty.usbmodem1421"

From here, I usually plug the C5 cell back in again and run the command to flash it as follows (of course you'd want to replace the .hex filename with the one you're using) 

"avrdude -U flash:w:vi-firmware-type4-CROSSCHASM_C5_CELLULAR-ctv7.2.0-csv7.0.0.hex -c stk500 -p 32MX795F512L -C avrdude.conf -P /dev/tty.usbmodem1421"

Where "/dev/tty.usbmodem1421" is at the end rather than the "0x10000af7" value you use. As for the part number, I'm using the same value "32MX795F512L" that you are.

Hope this works! 

Dominic

Kyle Kelly

unread,
Nov 22, 2016, 12:41:45 PM11/22/16
to OpenXC
You've saved me again! Thanks for the help, I was using a different command to try to pull the ID, I should have just followed the instructions. 

Kyle

Robert Baruch

unread,
Jan 11, 2017, 5:54:36 PM1/11/17
to OpenXC

I'm having the same problem, but I'm specify the /dev/tty.usbXXX port and avrdude complains it can't find the part.

avrdude -U flash:w:vi-firmware-type9-CROSSCHASM_C5_BLE-ctv7.2.0-csv7.0.0.hex -c stk500 -p 32MX795F512L -C avrdude.conf -P /dev/tty.usbmodem1451

avrdude: AVR Part "32MX795F512L" not found.


Am I doing something wrong? I'm doing this on the Mac, not the Vagrant.

Rob


On Friday, November 18, 2016 at 2:14:47 PM UTC-5, Dominic Meroux wrote:

Dominic Meroux

unread,
Jan 11, 2017, 6:11:20 PM1/11/17
to OpenXC
Hi Robert, 

Before you entered the command you posted, I presume you've entered ls /dev/tty.usb* at the terminal while the C5 device was plugged in with the light blinking, and the result for you was /dev/tty.usbmodem1451 ? 

I'm using a Mac as well.

Best, 

Dominic 

Robert Baruch

unread,
Jan 11, 2017, 7:51:48 PM1/11/17
to ope...@googlegroups.com

Indeed i did... Five seconds... That's ridiculous by the way... Maybe if there was a rest button, but hard power up... Just ranting grrr
--
You received this message because you are subscribed to a topic in the Google Groups "OpenXC" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openxc/qPdXeuTrAAM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openxc+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/openxc.
To view this discussion on the web visit https://groups.google.com/d/msgid/openxc/b6d69323-562f-42ab-91f4-e7bd4aaaf2a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Robert Baruch

unread,
Jan 14, 2017, 1:57:28 PM1/14/17
to ope...@googlegroups.com
Dominic,

Have you been able to successfully use the device in your Mac in a vagrant?

Do you see a device in /dev/tty after the 5 second programming window? I don't, but I do see the device is there when I list it using lsusb

Also when I run the dashboard i only get fake data. I run the command with the --usb option, but it didn't appear to be using the device.


Thanks for any insights,
Best,
Rob

I must be doing 

On Jan 11, 2017, at 6:11 PM, Dominic Meroux <dme...@gmail.com> wrote:

--

Dominic Meroux

unread,
Jan 14, 2017, 4:15:25 PM1/14/17
to OpenXC
Hi Robert, 

Have you been able to successfully use the device in your Mac in a vagrant?
I've used vagrant to compile custom firmware for the C5 devices, but not to "use the device" in. I didn't realize you could do this - are you referring to using the OpenXC Python commands in vagrant? 

Do you see a device in /dev/tty after the 5 second programming window? I don't, but I do see the device is there when I list it using lsusb
After the 5 second window, the device no longer shows up for me as well. I either run ls /dev/tty.usb* and then unplug the device, plug it back in, and then run the full command to flash it e.g. avrdude -U flash:w:vi-firmware-CROSSCHASM_C5_CELLULAR.hex -c stk500 -p 32MX795F512L -C avrdude.conf -P /dev/tty.usbmodem1421 or try to run both commands in the same 5-second window. Not an elegant approach but it works - I'm with you on the 5-second window being pretty short. 

Also when I run the dashboard i only get fake data. I run the command with the --usb option, but it didn't appear to be using the device.
By "when I run the dashboard I only get fake data" - are you referring to running the command "openxc-dashboard" or something else? Is the device plugged into the vehicle connected by usb or just your laptop? If it's generating fake data, I'd imagine it currently has emulator firmware?   

Best, 

Dominic

Robert Baruch

unread,
Jan 15, 2017, 11:45:51 AM1/15/17
to ope...@googlegroups.com

Dominic,

Got it to work! turns out that the part description definition on the avrdude.conf file was incomplete. When I found the definitions for the device and used an appropriate configuration, it found the part and wrote the firmware to the device successfully!

Now to experiment with the tools and see what else I get… How are you using the dongle? I recently purchased a new truck (Ford F150 BlackOps) and thought it would be fun to interact with it and noodle around with some customizations.

Rob


Dominic Meroux

unread,
Jan 17, 2017, 3:48:01 AM1/17/17
to OpenXC

Hi Robert,


Glad you found a fix! 


As for how I'm using the C5 devices + reference VI, here are some examples:


SMS Taxi project: https://github.com/dominicmeroux/SMS_Taxi


Firmware development: I've been trying to configure firmware that extracts interesting information while minimizing frequency of unnecessary messages. This is work in progress, but here's where I'm at: https://github.com/dominicmeroux/Custom-OpenXC-Firmware


C5 BT: I've been using this for reading data to an SD card. I want to see how quickly the SD card fills up using Ford vehicle-specific firmware (Type 6 for a Ford Fiesta), with an end goal of potentially using it in a fleet application for evaluating how vehicles are used. The SD card is a cheaper way of collecting data than requiring a phone or sending by cellular. 


C5 Cellular: I've been working with AT&T Flow and M2X with this VI, it's nice to be able to have data sent via cellular connection rather than collected by a phone or other tablet. 


Pretty neat about your new F-150 BlackOps! Best of luck on your OpenXC app development efforts - you have an awesome vehicle to work with! 


Dominic 

Robert Baruch

unread,
Jan 17, 2017, 10:24:07 AM1/17/17
to ope...@googlegroups.com


Dominic,

Can you share an example of calling openxc-diag with the c5ble stock firmware loaded on the VI? The docs on the website don't seem to reflect the calling psrameters.

Also,  are you running the openxc-* commands with sudo? I can't access the USB device unless I do so. Is that the way the device is configured?

Best,
Rob

Eric Marsman

unread,
Jan 17, 2017, 2:11:31 PM1/17/17
to OpenXC
Rob, Dominic,

Good conversation. Happy to see the activity! I have several comments.

Vagrant USB: While it is possible to pass USB control to the vagrant guest, we don't recommend it. It requires some modifications to the vagrantFile for VirtualBox. Working natively in the host is more reliable for us. If you find otherwise, let us know. 

5 seconds on C5s: Yes, this is an annoyance. We also get people who are annoyed at having to push the reset button on the Reference VI. Both of these options allow us to keep the bootloader simple. But yes, they take some getting used to.

openxc-diag: Did you check here: http://python.openxcplatform.com/en/master/tools/diag.html. This shows the command arguments. As for what PIDs to send, you could start here: https://en.wikipedia.org/wiki/OBD-II_PIDs. Most of Mode 1 is good. 

Dominic, thanks for your project links. Interesting work. 

Regards,
Eric

To unsubscribe from this group and all its topics, send an email to openxc+unsubscribe@googlegroups.com.

Robert Baruch

unread,
Jan 17, 2017, 2:57:43 PM1/17/17
to ope...@googlegroups.com

Eric,

Thanks for the clarification. I have installed the python tools natively onto OS X on my mac. A few observations:

When I run any openxc-* with my VI running the Type-3 ford firmware, it works, however, it initially dumps Can’t ead logs from data source -- stopping: ("USB device couldn't be read", USBError(60, 'Operation timed out’))

Secondly, I’ve seen the link that you reference for diags http://python.openxcplatform.com/en/master/tools/diag.html - however upon closer inspection, the examples use DIFFERENT parameters than the code. Specifically, --message-id is actually —message. Hense the confusion.

Best,
Rob

To unsubscribe from this group and all its topics, send an email to openxc+un...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
-- 
You received this message because you are subscribed to a topic in the Google Groups "OpenXC" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/openxc/qPdXeuTrAAM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to openxc+un...@googlegroups.com.
Visit this group at https://groups.google.com/group/openxc.
Message has been deleted

Robert Baruch

unread,
Aug 28, 2018, 1:13:47 PM8/28/18
to ope...@googlegroups.com
Hi,

It's been a while since I played with it, but I think the solution was an edit to the avrdude config file for the device.

What I changed I can't recall, but I vaguely recall editing the definition.

Best,
Rob

On Aug 25, 2018, at 7:57 PM, JOHNAVATAR.com <johnava...@gmail.com> wrote:

Hello Robert,

I'm having the exact same problem you were having over a year ago!  What exactly did you do to make this all work; "part description definition on the avrdude.conf file was incomplete"
What was incomplete and how did you complete it?

I'm thinking just the AVR Part Number needs to be changed to a correct number?

I get this error message:

JOHNAVATAR.com

unread,
Aug 28, 2018, 2:01:19 PM8/28/18
to OpenXC
Hello Robert,

Thanks for the reply.  I got it worked out.  OpenXC and FORD Dev provide clues, I just had to follow the clues to get it to work.  Plus the firmware provided doesn't work, I need a newer version, which I've received a newest Emulator firmware and that works.  Getting the Demo App to work is painful as well, but I got that to work.  So now I'm waiting for a new FORD Type 6 firmware version to work with my new 2018 FORD EcoSport Titanium.

Eric Marsman has been helping me with clues.

Sincerely,

<(•_•)>

Robert Moore

Silicon Beach Design Studio™ @

JOHNAVATAR.com™

Santa Monica, CA 90402

USA

Robert Baruch

unread,
Sep 3, 2018, 1:03:38 PM9/3/18
to ope...@googlegroups.com

Robert,

I had some time to take a look at this and I’ve confirmed that I can flash the device…

heres’ the script that I wrote to do so…

#!/bin/bash
echo Firmware file name: 
read filename
echo Device location \(eg. /dev/tty.usbmodem1421\): 
read location

if [ -z "$location" ];
then
        location="/dev/tty.usbmodem1421"
fi
read -n1 -r -p "Press any key within 5 seconds of connecting the device to start the flash..." key

echo "flasdhing to $location" && avrdude -U flash:w:$filename -c stk500 -p 32MX795F512L -C avrdude.conf -P "$location”




Also, If I’m recalling correctly, you need to use avrdude version 5.10 - as opposed to a later version.



Here’s the output from flashing a file:

$ ./flashDevice.sh 
Firmware file name:
vi-firmware-CROSSCHASM_C5_BLE.hex
Device location (eg. /dev/tty.usbmodem1421):

Press any key within 5 seconds of connecting the device to start the flash...
flasdhing to /dev/tty.usbmodem1421

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x504943
avrdude: NOTE: FLASH memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "vi-firmware-CROSSCHASM_C5_BLE.hex"
avrdude: input file vi-firmware-CROSSCHASM_C5_BLE.hex auto detected as Intel Hex
avrdude: writing flash (285840 bytes):

Writing | ################################################## | 100% 15.12s

avrdude: 285840 bytes of flash written
avrdude: verifying flash memory against vi-firmware-CROSSCHASM_C5_BLE.hex:
avrdude: load data flash data from input file vi-firmware-CROSSCHASM_C5_BLE.hex:
avrdude: input file vi-firmware-CROSSCHASM_C5_BLE.hex auto detected as Intel Hex
avrdude: input file vi-firmware-CROSSCHASM_C5_BLE.hex contains 285840 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 1.14s

avrdude: verifying ...
avrdude: 285840 bytes of flash verified

avrdude: safemode: Fuses OK

avrdude done.  Thank you.


Note that you have 5 seconds from the time that you plug in th device to your computer to access the UART…

Also, I’ve attached my avrdude.conf file for your reference.

avrdude.conf

Robert Baruch

unread,
Sep 3, 2018, 1:51:10 PM9/3/18
to ope...@googlegroups.com, johnava...@gmail.com
Robert,

Do you have the current link for the ford firmware? I want to try and flash the type-3 you see if there is a richer dataset available.

Best,
Rob

JOHNAVATAR.com

unread,
Sep 3, 2018, 4:06:55 PM9/3/18
to OpenXC
RobertB,

My car is a new 2018 FORD EcoSport Titanium and I'm using the "CrossChasm C5 BLE" VI and a MacPro running macOS High Sierra 10.13.6 and iOS and Xcode 9.4.1.

I'm thinking you're on a Windows PC and using Android? I'm on a MacPro and iOS on iPhone/iPad.  There are differences.

Contact Eric Marsman for a newest Type 3 firmware.  He provided with a new version that does work, but only he can provide that to you.

Eric also provided me with a correct "avrdude.conf" file, the one that I had was not correct.  I was using all files I download from the FORD Dev, OpenXC and GitHub websites, none were correct, close, but not 100%.  That led to a lot of confusion for me, once I had the correct files that FLASH to my VI was easy and the connect to my iPhone to the VI was easy....

Yes, I used "avrdude-5.10".

THOUGH I still had to do a lot of work to get the iOS Demo App to work... it does not work as downloaded.... there is a lot of work to get to working.

ALSO, on a Mac, it turns out there are 2 "avrdude.conf" files that I guess need to be replaced (I did both) in the FLASH directory which when the ZIP I downloaded from GitHub named as "OpenXC-CrossChasm-Flash".  There is a "avrdude.conf" at the root and another in the folder named "avrdude-5.10".  Then I place the firmware file "vi-firmware-type3-CROSSCHASM_C5_BLE-ctv7.2.1-dev-csv7.0.0.hex" (Eric provided) in the root of  "OpenXC-CrossChasm-Flash" and all that worked to FLASH my VI.
OpenXC-CrossChasm-Flash Screen Shot 2018-09-03 at 1.03.01 PM.png
avrdude-5.10 Screen Shot 2018-09-03 at 1.03.21 PM.png

JOHNAVATAR.com

unread,
Sep 3, 2018, 4:09:41 PM9/3/18
to OpenXC
Everything is working for me now, the VI and the iOS App.

I'm just getting started to do more R&D.... I'm just at the beginning and this is not a full-time project, unless I can get funding, then I'd go full-time on this.

Sincerely,

<(•_•)>

Robert Moore

Silicon Beach Design Studio™ @

JOHNAVATAR.com™

Santa Monica, CA 90402

USA



JOHNAVATAR.com

unread,
Sep 3, 2018, 4:16:14 PM9/3/18
to OpenXC
Both the "avrdude.conf" and the firmware version you have "vi-firmware-type9-CROSSCHASM_C5-ctv6.0.3-csv6.0-1-gb3f9b6b.hex"
may not be correct!

I was getting the same error.  

Eric Marsman provided me with replacement files for both of those files and I was then able to FLASH my
"CrossChasm C5 BLE" VI


My car is a new 2018 FORD EcoSport Titanium and I'm using the "CrossChasm C5 BLE" VI and a MacPro running macOS High Sierra 10.13.6 and iOS and Xcode 9.4.1.

I hope this helps?


<(•_•)>

Robert Moore

Silicon Beach Design Studio™ @

JOHNAVATAR.com™

Santa Monica, CA 90402

USA


On Thursday, November 17, 2016 at 12:50:40 PM UTC-8, Kyle Kelly wrote:
Message has been deleted

JOHNAVATAR.com

unread,
Sep 3, 2018, 4:30:13 PM9/3/18
to OpenXC
I believe I downloaded that from the FORD Developer website, but for some reason my password doesn't work so I can't verify?  I've tried to reset and contact FORD Dev, they don't have an answer.  So right now, I'm not able to access the FORD Developer website to confirm.  Plus my password no longer works at the SDL website.  I believe they force a password change every 90 days, which appears to be very buggy, because it wasn't 90 days since I last tried to access both and I'm not able to update my password, I just get error messages!

Robert Baruch

unread,
Sep 3, 2018, 4:34:27 PM9/3/18
to ope...@googlegroups.com
Lastest on the website is from 2016...

Robert Baruch

unread,
Sep 3, 2018, 4:36:16 PM9/3/18
to ope...@googlegroups.com
Robert,

Might be beneficial to fork the iOS demo and put up your version that works saving us all a ton of time :)

Rob

On Sep 3, 2018, at 4:30 PM, JOHNAVATAR.com <johnava...@gmail.com> wrote:

Robert Baruch

unread,
Sep 3, 2018, 5:39:02 PM9/3/18
to ope...@googlegroups.com
okay - I was impatient so I built the iOS demo app…  ;-)

JOHNAVATAR.com

unread,
Sep 3, 2018, 6:34:18 PM9/3/18
to OpenXC
I would have to get permission from OpenXC or FORD Dev (or someone?) to upload the Demo App I have that's working.  I just now did do some cleanup to prepare for that  (in the build it had placed it's framework files to my system folder, rather than the app location, which I just now corrected).

Let me know if you get it working.

My interest is Self Driving R&D.  I had a FIAT 500e and was communicating to FCA, but when they signed a deal with Google, that kind of ended.... So now I'm on to FORD!:*)

<(•_•)>

Robert Moore

Silicon Beach Design Studio™ @

JOHNAVATAR.com™

Santa Monica, CA 90402

USA


JOHNAVATAR.com

unread,
Sep 3, 2018, 6:39:21 PM9/3/18
to OpenXC
I was just looking and the FORD Firmware that I downloaded is what was not working and which Eric Marsman provided an updated version that does work.

None of the posted firmware worked for me, FORD, or OpenXC.  Marc sent me working firmware.

Robert Baruch

unread,
Sep 3, 2018, 7:09:18 PM9/3/18
to ope...@googlegroups.com

I got it working...

The docs encourage you to fork the repo (which I did), so you don't need permission to manage your own fork however motified.
.

Robert Baruch

unread,
Sep 3, 2018, 7:50:02 PM9/3/18
to ope...@googlegroups.com

My firmware isn't working either for my 2017 F-150...

Eric Marsman

unread,
Sep 5, 2018, 11:39:00 AM9/5/18
to OpenXC
Robert B.,

There were some updates to the firmware specific to the C5 BLE device for iOS. I can send you an updated type3 if you provide your email address and proof that you have agreed to the terms here for downloading compiled firmware. You can email me at emarsman at ford. https://developer.ford.com/pages/ford-terms-of-use/. 

Regards,
Eric
To unsubscribe from this group and all its topics, send an email to openxc+unsubscribe@googlegroups.com.

Eric Marsman

unread,
Sep 5, 2018, 11:41:29 AM9/5/18
to OpenXC
Robert M.,

You do not need any permission to share derivatives of the OpenXC software published under the BSD license. Robert B. is correct. You can fork on github and share your link here. 

If you have things you had to fix, please let us know. You can issue a pull request if you want. Modifications shouldn't be necessary. 

Regards,
Eric

Robert Moore

unread,
Sep 5, 2018, 11:51:36 AM9/5/18
to ope...@googlegroups.com
Hello Eric,


Thank you...Besides other things, I'm a graphic designer.


I would like the new type 3 emailed to me and a list of command I am able to send to my 2018 FORD EcoSport.


My email is: JohnA...@JohnAvatar.com


There is no accept button at the agreement webpage and when I select download, I get an error (see attached image).


Sincerely,

•• 

Robert Moore 

Silicon Beach Design Studio @

JOHNAVATAR.com 

Santa Monica, CA 90402

USA


Sent from iPhone


image1.png

You received this message because you are subscribed to the Google Groups "OpenXC" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openxc+un...@googlegroups.com.

Robert Baruch

unread,
Sep 5, 2018, 12:24:24 PM9/5/18
to ope...@googlegroups.com, emar...@gmail.com

Hi Eric,

Thanks for the updated firmware -- I have a 2017 F-150 truck -- I'm assuming I need a type-3 firmware, but if I'm wrong, please send the proper valid firmware to


I'm a member of the Ford development program (associated with the email above) and have agreed to the terms and conditions to all downloads.

Best,
Rob

Eric Marsman

unread,
Sep 5, 2018, 12:41:43 PM9/5/18
to OpenXC
Robert M,

I already sent you the type3.

Regards,
Eric
To unsubscribe from this group and stop receiving emails from it, send an email to openxc+unsubscribe@googlegroups.com.

Robert Moore

unread,
Sep 5, 2018, 2:18:37 PM9/5/18
to ope...@googlegroups.com
I thought you had another update.

The Type 3 works fine.


Thank You,

•• 

Robert Moore 

Silicon Beach Design Studio @

JOHNAVATAR.com 

Santa Monica, CA 90402

USA


Sent from iPhone

To unsubscribe from this group and stop receiving emails from it, send an email to openxc+un...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages