NefMoto > Technical > NefMoto Software > NefMoto Flasher trouble? What happened?
Pages: [1] 2
« previous next »
Author Topic: NefMoto Flasher trouble? What happened?  (Read 13965 times)
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« on: March 04, 2013, 11:48:35 AM »
Hi -

I attach the log of the event when NefMoto flashed a *.bin and then, directly after, could not connect again.
Can anyone read out what the trouble is?
The last actual flashing starts at 04-mar-2013 10:30, ends at 10:33:50.
Nine seconds later, the next attempt to connect to the ECU fails, as have all attempts since.

Does that make sense to anyone? I can't say I understand all the information in the logfile.

The car was working the second before (10:29) the flash started, with the software I flashed yesterday.

The only difference in the code was an increased tolerance in the KFDLULS to avoid the earlier overboost error. Prepared after the same template, checksum corrected with ECUfix.

I tried uninstalling the drivers and NefMoto, so far to no avail.

Later I also re-flashed the same bin with Galetto, but haven't been able to start the engine yet.

Now what? After all the attempts I still have no hot clue where the main issue may be.

/Klaas
Logged
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140
« Reply #1 on: March 04, 2013, 12:07:42 PM »
"04-mar-2013 07:36:06.714: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
04-mar-2013 07:36:06.715: LOG: FTDI ChipID DLL is loaded, checking chip ID...
04-mar-2013 07:36:06.716: LOG: Unable to read FTDI device chip ID
04-mar-2013 07:36:06.975: USER: Validated FTDI device is in dumb mode.
04-mar-2013 07:36:06.984: LOG: Starting send receive thread.
04-mar-2013 07:36:06.993: LOG: Send receive thread now started.
04-mar-2013 07:36:06.995: USER: Disconnected
04-mar-2013 07:36:07.013: LOG: Setting communication timings to defaults.
04-mar-2013 07:36:07.015: LOG: Set timing parameters to defaults.
04-mar-2013 07:36:07.016: USER: Connecting...
04-mar-2013 07:36:07.036: LOG: Setting communication timings to defaults.
04-mar-2013 07:36:07.040: USER: Starting slow init connection.
04-mar-2013 07:36:09.640: USER: Connecting to address 0x01.
04-mar-2013 07:36:11.798: USER: Slow init succeeded."
The cable is probably an FT232/245bm, and the "device id" couldn't be read because the bm series of these chips doesn't have a serial number (or something like that) but the device id couldn't be read whether Nefmoto connected or not.

are you using the drivers supplied with the cable?
IMO, you should be using these latest FTDI drivers.

I'm pretty sure that flashing a bad file can cause this as well, I think this was the cause of my first brick.
recoverable via Galletto-bootmode.
« Last Edit: March 04, 2013, 12:12:44 PM by cyril279 » Logged
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« Reply #2 on: March 04, 2013, 12:28:18 PM »
No, as far as I know I had a fresh install av the latest drivers (same link) and the current NefMoto flasher.
Later, I tried older drivers, not better anyway...
By the way, the part of the log file you cited was BEFORE my successful engine starts this morning. The trouble started then...

/K
Logged
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140
« Reply #3 on: March 04, 2013, 12:54:19 PM »
Whether before or after, each connection point shows that Nefmoto was able to connect to, identify, and validate the cable.
The inability to read the device ID occurred whether Nefmoto connected to the ECU or not.
based on all of the connection attempts in the log, Nefmoto doesn't seem to be bothered by the cable, which is the reason that I wonder whether the flash itself is the issue.
 
04-mar-2013 07:17:05.439: LOG: Opened FTDI device.
04-mar-2013 07:17:05.440: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
04-mar-2013 07:17:05.440: LOG: FTDI ChipID DLL is loaded, checking chip ID...
04-mar-2013 07:17:05.440: LOG: Unable to read FTDI device chip ID
04-mar-2013 07:17:05.463: USER: Validated FTDI device is in dumb mode.
04-mar-2013 07:17:05.467: LOG: Starting send receive thread.
04-mar-2013 07:17:05.468: LOG: Send receive thread now started.
04-mar-2013 07:17:05.469: USER: Disconnected
04-mar-2013 07:17:05.488: LOG: Setting communication timings to defaults.
04-mar-2013 07:17:05.488: USER: Connecting...
04-mar-2013 07:17:05.502: LOG: Setting communication timings to defaults.
04-mar-2013 07:17:05.503: USER: Starting slow init connection.
04-mar-2013 07:17:08.103: USER: Connecting to address 0x01.
04-mar-2013 07:17:10.906: LOG: Failed to read sync byte, guessing baud rate is actually 9600.
04-mar-2013 07:17:10.948: LOG: Not enough key bytes, read: 0
04-mar-2013 07:17:10.955: USER: Slow init failed.
04-mar-2013 07:17:10.956: USER: Disconnected
Logged
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« Reply #4 on: March 04, 2013, 12:57:07 PM »
"the flash itself"

Not sure I get the meaning correctly. The data, writing, or both?
Sorry, not a native speaker so sometimes I just have to ask

/K
Logged
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140
« Reply #5 on: March 04, 2013, 01:02:22 PM »
The cable and drivers seem alright. I'm wondering whether the last file (.bin) that you flashed to the ECU is good or not. Once you apply a bad .bin file to an ECU, then it may need to e recovered using a bootmode tool (Galletto).
Logged
cyril279
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 140
« Reply #6 on: March 04, 2013, 01:13:27 PM »
Can you connect to the ECU with VCDS lite or VAG k+Commander?
Logged
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« Reply #7 on: March 04, 2013, 01:16:57 PM »
I'll put it on the list for tomorrow evening, will attend the family now I guess

Thanks for all the help so far!
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640
« Reply #8 on: March 04, 2013, 05:41:17 PM »
Codes.

Does the engine light come on with the key? If not, you need to bootmode the ecu, then re-write the bin again with nefmoto.

What year/ecu is in your car?
Logged
Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« Reply #9 on: March 04, 2013, 09:31:47 PM »
Quote from: ddillenger on March 04, 2013, 05:41:17 PM
Codes.

Does the engine light come on with the key? If not, you need to bootmode the ecu, then re-write the bin again with nefmoto.

What year/ecu is in your car?

2004/4Z7907551N

I think the engine light comes on with the key, but will check that again.
Logged
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655
« Reply #10 on: March 04, 2013, 09:42:46 PM »
how many threads have you had all stating that after you flash the ecu is a brick? obviously there is a crucial piece of the puzzle missing here. ie: why your flash is causing a brick.
i guess what im trying to say here is that the common consensus here seems to be a problem with your bin.
all these posts over complicating flashing. how long to leave the key on after bench flashing? that isnt going to determine whether your car starts or not.
« Last Edit: March 04, 2013, 09:50:55 PM by k0mpresd » Logged
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« Reply #11 on: March 04, 2013, 09:59:43 PM »
C0mpressed - that's a bit harsh. I'm trying to learn, but you want to help me by walking me through it. That's allright, but I can walk myself only I have the observations/expectations right. Else I'll just be uncertain about what happened and will be back in the forum.

Alright, I'll check the bin tonight. Again. (If it is an error in it, why did it run yesterday morning?)

I assume it is no idea to move to the car unless I can connect with NefMoto on the bench. Now that would be good, because then I could test different things much faster.

When an ECU is fine after bench flashing, how does it behave in the car? Any rituals to follow?
Logged
k0mpresd
Hero Member
*****

Karma: +146/-54
Offline Offline

Posts: 1655
« Reply #12 on: March 04, 2013, 10:03:04 PM »
Quote from: KBUR on March 04, 2013, 09:59:43 PM
When an ECU is fine after bench flashing, how does it behave in the car?

it starts the car.
Logged
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« Reply #13 on: March 04, 2013, 10:03:32 PM »
Quote from: k0mpresd on March 04, 2013, 09:42:46 PM
how many threads have you had all stating that after you flash the ecu is a brick? obviously there is a crucial piece of the puzzle missing here. ie: why your flash is causing a brick.
i guess what im trying to say here is that the common consensus here seems to be a problem with your bin.
all these posts over complicating flashing. how long to leave the key on after bench flashing? that isnt going to determine whether your car starts or not.

By the way - how long I left the key on after flashing is the only parameter I am aware of I changed before the car startet yesterday morning. Thats exactly what got me confused. Just wanted to know whether that plays any role (som say it does), and I still have no answer to that. If all these times are just mumbo jumbo, can anyone just state that, please?

Gotto go to work now
Logged
KBUR
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 32
« Reply #14 on: March 04, 2013, 10:08:28 PM »
Final though before I leave tha house - can I trust Galetto to judge whether the flash is successful? Any chance the flash produces a brick and I would not notice that in boot mode?
Hmmm.
Thats different layers. Seems possible?
Logged
Pages: [1] 2
  Print  
« previous next »
 
Jump to:  

Navigation
Personal Tools
  • November 23, 2024, 12:21:06 AM
  • Welcome, Guest. Please login or register.
    Did you miss your activation email?

    Login with username, password and session length
Search
 
Advanced Search
About Disclaimer
All Rights Reserved 2010 Nefarious Motosports
Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.022 seconds with 16 queries. (Pretty URLs adds 0s, 0q)