Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Yamaha/Moric single cylinder ecus ?? YZF R125 in mind


Guru

Status: Offline
Posts: 2338
Date:
RE: Yamaha/Moric single cylinder ecus ?? YZF R125 in mind


XTAL can easily verified, just open up the silicone where the XTAL is and see the frequency.

I tested different resets on the erased ecu.

Last eday from TMT was on friday asking for mask and mcu id. Lets hear when weekend is over.

I think there may be an issue with BDM units or with my driver installation. I got once a connection with Test_USBDM.exe, but not again. Too many unstable parts in the chain.




__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 49
Date:

Hello, Splurk
good work, like Petrik say maybe the German company just change Crystal of the ecu so rpm limit go higher. original crystal are 4 MHz if change crystal value rpm limit change but other restrict continues like the 4 º retard in ignition curve that was put so power don't pass 15CV.
the camshaft sensor don't have any adjust so the only way of remove this 4º retard is change ignition curve map inside ecu or in last way cut the base of camshaft sensor so a advance can be done but cut the base of sensor is very risk because can with time get lose and break too many parts of rotor and motor.
looking for the area they cut in ecu i think they only change crystal but if BDM are in board lets find a way of use it :)
Impossible is nothing.



__________________


Veteran Member

Status: Offline
Posts: 49
Date:

I already talk to my friend that reprogram all type of cars and he have professional tools but the tools that he have only can connect to Yamaha r6 and r1 ecu he don't have cable for this kind of ecu because the tools are professional he can't do alterations in cables, but he say is possible if solder wires from the board to ecu to some pro tools that have a adapter with a cable to solder, but he don't have that adapter.
he say this CPU h12t64 is use in some Yamaha r6 ecus as secondary CPU in case of r6 this CPU control immobilizer and he say there are people that can re-prom that CPU in r6 in a new set of keys of the motorcycle.



-- Edited by mikaspt on Sunday 5th of September 2010 10:57:49 AM

__________________


Veteran Member

Status: Offline
Posts: 49
Date:

Petrik can you find here FI TOOL wire connect in ECU board layout?
PIN 18 in ecu connector to ??? BDM or CPU pin?

-- Edited by mikaspt on Sunday 5th of September 2010 11:01:14 AM

__________________


Guru

Status: Offline
Posts: 2338
Date:

The FI Diag signal connects to two pins of an undefined IC with markings
2028
J8K1
607Y
On the other side of the IC I can see two resistors which hook up to processor PIN16 / PP4.

Believe that this is a TTL to +12V conversion circuit. When have the oscilloscope rigged up can look a bit more into this.

Would like to get BDM running. It does not make sense that have so unstable connection.



__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 49
Date:

Petrik i think that IC is the volt monitor that put ecu in SPI mode let me try find more information.


__________________


Guru

Status: Offline
Posts: 2338
Date:

Reset line stuck is not really missing reset signal. I can see that the FI Diagnostics tool is loosing the contact when Reset is applied. So Reset Line Stuck is rather related to the inability of BDM to respond.

After a reset I need physically remove the BDM board to get ECU running again. Somehow the BDM is getting stuck.

On Freescale Codewarrior I get message "Running - Manual Secured".

When running MODA = 0v, MODB = 0v. ModC is set by BKGD as its the same pin. So I would guess that the interface sets MODC somehow after reset.

But as I am unable to flash the with unsecure command there must be more to this.




__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Member

Status: Offline
Posts: 19
Date:

What is the BDM board you have? I agree that we need to find out what's going on with this reset.

__________________


Guru

Status: Offline
Posts: 2338
Date:

In this document is a fairly good description of BDM

http://www.gcc-hcs12.com/documnets/Freescale/S12CPU15UG.pdf

__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Guru

Status: Offline
Posts: 2338
Date:

cncgeeks HCS12 board is the one which worked in past at least.

__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Guru

Status: Offline
Posts: 2338
Date:

This tool looks very handy with TBDML interfaces.
http://macmadigan.no-ip.com/public/yamahar125/Test_USBDM.zip


Maybe the fact that SPMODE in CN2 is overlooked - or why otherwise that would be brought to the CN2 ?

- CN2 Pin1 -> Processor pin 7 MODC/BKGD (5V level)
- CN2 Pin2 -> GND (0V level)
- CN2 Pin3 -> Processor pin 8 SPMODE/SCKBDM (0V level)
- CN2 Pin4 -> Processor pin Reset, 1KOhm buffer and then 5KOhm pullup to +5V (3.4V level)
- CN2 Pin5 -> Processor pin 9 SO (0V level )
- CN2 Pin6 -> +5V, Processor pin 77 Vddx (5V level)



__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 68
Date:

digislayer wrote:

Check this info:

BDM is very useful as a debugger, but it takes a bit of thought

Several common possibilities for "sporadic" and "never never land":

1) Are your MODA and MODB pins tied low? BDM only works reliably if the
chip starts in Special Single Chip mode. You code (or your debugger) can
change the mode after reset, but you need to start in Special Single Chip
so that the micro doesn't take off and start executing until you tell it to.

2) Does your code enable the COP? It is disabled when you come up in
Special Single Chip. However, if you enable it and don't service it, a
reset will occur (duh). However, during this reset, the BGND line will
probably NOT be low, so the chip will start in NORMAL Single Chip mode
rather then Special Single Chip. So, BDM won't be enabled, and since you
got a reset, all your hardware breakpoints are gone.

"You may be having communication issues. Are you using a standard
development board, or one of your own design? Ensure that you have
pull-ups on the RESET and BKGD lines."


source: http://www.embeddedrelated.com/groups/68hc12/show/6646.php




Did you read the above petrik?? And also, which ECU were you using for what you wrote in the above post? The one that you erased? or the one that is open and unerased?

 

 

EDIT: Petrik, what happens when you connect the ECU to the BDM module and use HCS12MEM forcibly? Forcibly in the sense, type the -f command in HCS12MEM and reset the ECU manually and see if it can read then. Because, BDM is not supposed to be available in secured mode, hence it is natural for the BDM module and COdeWarrior to not detect a connection. But since HCS12mem has a force -f switch, let us try...

EDIT 2: Also, did you try using the Freescale SerialMonitor software? It creates a watchdog or something...






-- Edited by digislayer on Sunday 5th of September 2010 05:08:32 PM

__________________
Sunny.


Guru

Status: Offline
Posts: 2338
Date:

Thanks, as confirmed above:

ModA, ModB = 0v

ModC/BKGD = +5V when no bdm interface connected. I can check the pullup resistance.

Reset = 3.4V when no bdm interface connected. It has a 5KOhm pullup as described above.

Learned that Test_USBDM does not give good responses for most BDM commands and claims that BDM is busy. So its possible that there is a driver or interface issue...


__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 68
Date:

Use the SerialMonitor program by Motorola. I just learned that it can reset MCU and supports a few primitive debug commands..

Check this for documentation/description:
http://docs.google.com/viewer?a=v&q=cache:T8A9ZvA6VScJ:www.freescale.com/files/microcontrollers/doc/app_note/AN2548.pdf+HCS12+reset+stuck+secured&hl=en&gl=in&pid=bl&srcid=ADGEEShoja6BwI1nDmBDCaVrTxs1gpqiOv-qeGH0hV_HbVO-TgRIWiW6tOLHxpVmx29bSdL4FMC0Rzqt_i3leBHUl2WqbF_3Wwf1_Ie7XPMvhsa-RfbbWZrVXlwrAthZ-N67SyP4D4T3&sig=AHIEtbT2C-xl9YhJ5_SAVcDDBGOmqLfv9Q

Reading the first introduction page alone will give you an idea.

__________________
Sunny.


Veteran Member

Status: Offline
Posts: 68
Date:

Another thing that I just learned Petrik:
Even ModC must be grounded for BDM. (But I still doubt BDM will not work in our case since the MCU might be secured)


By the way, why dont you try Mass Erasing the old ECU(the first one), and then try gaining a connection? That should tell us if the problem is with the BDM pod or with the ECU hardware itself. Because, Mass Erasing with an unsecure command will unsecure the ECU while erasing everything on the MCU. After that, we should be able to access its BDM. If we're still not able to access BDM, it means the problem is not with the "secured" state, but with the BDM chain..

__________________
Sunny.


Guru

Status: Offline
Posts: 2338
Date:

I have tried mass erasing (unsecuring) the opened up ecu several times. As I can not do that it first indicated potential issue with bdm interface card. Now as test_usbdm can not set speed, does not reply with firmware and is giving an error with connect I am really starting to doubt that the bdm pod is up to the task what we are trying to do here.

ModC is the BKGD pin i.e. set by BDM pod.

These are the on line command for test_usbdm.exe

Found 1 devices
#?
-?
connect - Connect to target
firmware - Check BDM firware
debug - Debug commands
delay - Pause a while
db - Read byte
dw - Read word
dl - Read longword (CFV1 only)
exit - Exit program
flashopen - Open RS08 flash
flashclose - Close RS08 flash
go - Start from current PC
gs - Read status register
halt - Halt the target
help - Display help
jtag-reset - Take JTAG TAP to TEST-LOGIC-RESET state
jtag-shift-dr - Shift given values into DR
jtag-shift-ir - Shift given values into IR
jtag-idcode - Read IDCODE from JTAG
regs - Print out registers
reset - Reset to bdm mode
rb - Read byte
rblock - Read block
rw - Read word
rl - Read longword (CFV1 only)
rreg - Read core register
rdreg - Read debug register
rcreg - Read control register
setboot - Set USBDM module to ICP mode
settarget - 0=HCS12, 1=HCS08, 2=RS08, 3=CFV1
speed - Set speed
step - Execute a single instruction
sync - Execute a low level sync
tblock - Random RAM write/read block test
testcreg - Test control register
testinterface - Directly control interface signals
teststatus - Read target status in an infinite loop
trim - Calculate clock trim value
wait - Pause a while
wb - Write byte
wblock - Write block
wc - Write control register
wpc - Write to PC
ww - Write word
wl - Write longword (CFV1 only)
wreg - Write core register
wdreg - Write debug register
wcreg - Write control register
#

__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 68
Date:

what happens with the command SETBOOT? Did you try it?

I'm in a confusion now. According to the rules, we wont have BDM access until MCU is unsecured. And also, MCU can be unsecured with a Mass Erase command . Now, how do we mass erase a secured MCU without BDM access?

Also, try unsecuring with HCS12MEM by giving all the parameter yourself. Dont expect HCS12MEM to detect any parameters or the device itself, give in all the parameters yourself. I just learned that BDM will not work with wrong frequency given to the software. The software must know the correct internal clock speed for the to work. Is it possible the internal clock speed is diff from what the external crystal shows?


Look at this information, it's helpful..I just read it:

"Having erased flash and non-empty eeprom, and reseting the part into
single chip special mode, BDM will come out of reset as disabled
(BDMSTS.ENBDM == 0) and inactive (BDMSTS.BDMACT == 0). That doesn't mean
BDM no longer works - only firmware commands are disabled, but hardware
commands are still allowed. FLASH and EEPROM operations are limited then
to mass erase only. In this state, you have to mass erase both EEPROM
and FLASH, reset the part once more, BDM detects that EEPROM and FLASH
are both erased and enters "unsecure" BDM mode (BDMSTS.UNSEC bit, that's
different from overall security of the chip). That unsecure mode now
allows you to reprogram 0xff0e FLASH byte to unsecured state, thus
unsecuring whole MCU, after next reset. That's unsecuring procedure.
I'm not sure if it works for every HCS12 derivative. Works for A64 and
NE64, which I currently have on my bench and am just writing such
procedures :)
I recall that there was some discussion here about problems with some
early mask versions, that could render some chips to doorstop. But I
assume there were "exceptions". I don't know if there are some
derivatives that are secure-only-once-and-forget-about-unsecuring by design."

SOURCE: http://www.embeddedrelated.com/groups/68hc12/show/11859.php

__________________
Sunny.


Veteran Member

Status: Offline
Posts: 49
Date:

there is the link for moda and modb connect ground
"
  1. Tie the MODA and MODB pins of your target to ground (Single Chip mode). If you are using these pins as port pins, you may need extra circuitry to hold the pins low during reset. In conjunction with the BDM pod, NoICE will start the chip in Special Single Chip mode. If you start in any other mode, the processor will begin executing instructions immediately, and NoICE may not be able to control it. "

http://www.noicedebugger.com/help/bdm12.htm#drivers



__________________


Veteran Member

Status: Offline
Posts: 49
Date:

noice hc12  download install and put in bin folder dll of your dongle.
http://www.noicedebugger.com/download.html


and choose TBDML AXION

-- Edited by mikaspt on Tuesday 7th of September 2010 08:20:38 PM

__________________


Veteran Member

Status: Offline
Posts: 49
Date:

Petrik did you try with NoIce software?

__________________


Guru

Status: Offline
Posts: 2338
Date:

Done that much earlier - same problems with that, thanks for searching it.

Unfortunately no reply from TMT.lt yet.

__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Guru

Status: Offline
Posts: 2338
Date:

To summarize what is the plan currently in the order of priority:

1) Need to get the flashing to an ecu working. That way I know that the interface is good and that any read flash and eprom images can be written.

2) Read the flash and eprom contents. Either can be done with BDM or on an adapter like http://www.etlweb.com/prod_prog_mc912/files/912_9s12_mqt.pdf

As of today 1) is has not been succesfull. Even with a secured processor the ERASE command using BDM should work. As of today getting an error message on the TBDML interface. Ordered another BDM interface in case there is something wrong with the one I have. The other interface does not support TBDML and therefore useless for the software I have. To me it looks like the interface hangs up so can be also a driver issue.


__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 49
Date:

i think the best interface for the price is P&E Multilink

__________________


Guru

Status: Offline
Posts: 2338
Date:

P&E could be - the interface is reasonably priced, but where to get the software ? If we need to use that for flashing it means 500USD cost for anyone who wants to flash the ecu in the first place. Alternatively the inDart has this processor listed, which is around 500 again.

If this high level of prices is needed then we could of course try to set up a service that someone just does the flashing as a service and then allow a separate software to e.g. tune for maps using the FI Diagnostics interface with a flashed ecu - kind of race ecu approach. Anyway we are far from that at this stage.




__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 49
Date:

so the best is find a low cost adapter that work good with hc12 and with Freescale software codewarrior.


-- Edited by mikaspt on Sunday 12th of September 2010 07:53:05 PM

-- Edited by mikaspt on Sunday 12th of September 2010 07:53:29 PM

__________________


Veteran Member

Status: Offline
Posts: 68
Date:

I was out of town for a few days...

@Petrik:
If the other BDM interface doesn't support TBDML, why did you order it? Alternatively there're a few XPROG-m clones available in the market available with full authorizations, at around 150-180 USD. But unfortunately, we cant say for sure if it will work with T64...but deifinitely does work with all other HCS12 family micros... just our luck!


And, what about TMT.lt ? Still no reply?

__________________
Sunny.


Member

Status: Offline
Posts: 19
Date:

Problem is that remains expensive, and we still don't know if it will do the job...
I say that because my approach would be more hardware... trying to do something from the parallel port of my PC, or using a USB to serial...
Using USB to BDM with libusb can also allow us full control of the debug device.

Problem: we need to program applications in C, and find out all the BDM specifications we can.

-- Edited by splurk on Tuesday 14th of September 2010 09:02:07 PM

__________________


Guru

Status: Offline
Posts: 2338
Date:

digislayer wrote:

I was out of town for a few days...

@Petrik:
If the other BDM interface doesn't support TBDML, why did you order it? Alternatively there're a few XPROG-m clones available in the market available with full authorizations, at around 150-180 USD. But unfortunately, we cant say for sure if it will work with T64...but deifinitely does work with all other HCS12 family micros... just our luck!


And, what about TMT.lt ? Still no reply?



Learning process, the other protocol which I do not remember is still working with codewarrior.

Please feel free to contact TMT.lt on my behalf.  Quite busy with day time stuff right now...



__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Member

Status: Offline
Posts: 12
Date:

It maybe worth looking at this link http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KIT33812ECUEVME.



__________________


Guru

Status: Offline
Posts: 2338
Date:

Excellent - thank you. ordered one immediately.

Ordered Part # : KIT33812ECUEVME
Part Description: SINGLE CYL S12 ENG CONTR

  • Assembled and tested evaluation board/module in anti-static bag.
  • Misc Cables (see packing list)
  • CD-ROM containing:
    • Supporting Documentation for featured device (may include datasheet, user's guides, app notes...etc)
    • Schematic of evaluation board
    • Bill-of-Material for evaluation board
    • Instruction sheet for evaluation board
    • Quick start guide
    • Software and configuration files (if applicable)
  • CodeWarrior development studio CD-ROM
  • USB based BDM tool for flash programming and debugging


-- Edited by PetriK on Sunday 19th of September 2010 08:48:42 AM

__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 49
Date:

PetriK wrote:

Excellent - thank you. ordered one immediately.

Ordered Part # : KIT33812ECUEVME
Part Description: SINGLE CYL S12 ENG CONTR

  • Assembled and tested evaluation board/module in anti-static bag.
  • Misc Cables (see packing list)
  • CD-ROM containing:
    • Supporting Documentation for featured device (may include datasheet, user's guides, app notes...etc)
    • Schematic of evaluation board
    • Bill-of-Material for evaluation board
    • Instruction sheet for evaluation board
    • Quick start guide
    • Software and configuration files (if applicable)
  • CodeWarrior development studio CD-ROM
  • USB based BDM tool for flash programming and debugging


-- Edited by PetriK on Sunday 19th of September 2010 08:48:42 AM

You still need software inside CPU, you will need to read a original ecu to get inside software.

 



__________________


Guru

Status: Offline
Posts: 2338
Date:

Yes, remembering the objectives:

1) Get flashing working with a cheap flashing tool
2) Get the firmware out of an existing ecu

No point to do 2) before 1) is fixed.

What is it that you guys have been up to lately with this project.


__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Member

Status: Offline
Posts: 12
Date:

Do you know if the Yamaha FI toll communicates using the K line and using a ISO protocol. It looks like that is what is suggested in the Motorola reference material.

__________________


Veteran Member

Status: Offline
Posts: 68
Date:

Well Petrik, I mailed the guys at TMT.lt , let's hope they reply soon now. It's festival time here, and I've been a little busy. I purchased the FI Diagnostic tool here 3 days back. It might be OT, but I just found out that this FI system is capable of making up for changes in air intake volume in spite of being an open-loop system.


And, I was actually waiting for something from your side. Since we people dont have the BDM or ECU with us, we cannot do anything until you post something.. If you need some help, we can readily provide it, like how it's been happening. I could buy the ECU and BDM, but I'm still a student and the ECU costs 7,000 rupees here (150 U.S. dollars), and you know it's not cheap. That's why, waiting for you to confirm upon a BDM tool first. Once the flash contents are read, I can help with the programming part too.

__________________
Sunny.


Veteran Member

Status: Offline
Posts: 68
Date:

Just to update all of you..still no reply from TMT.lt guys...

__________________
Sunny.


Guru

Status: Offline
Posts: 2338
Date:

TMT was kind enough to send a message that "we will contact you when there is something new".

Currently waiting for the Freescale kit to arrive sometime in October. That BDM is known to work for sure what ever it is.



__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 68
Date:

Well, That BDM might be compatible with only that type of microcontrollers. The chip that comes with the kit isn't T64, right? How can we be sure that the bundled BDM will work for T64 then?

__________________
Sunny.


Guru

Status: Offline
Posts: 2338
Date:


Like said earlier suspect to have an issue with the BDM driver with limited functionality. With the SDK can test the various BDM:s have and have a reference to a working one.


__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 68
Date:

But, the bundled BDM might be compatible with the chip supplied in the kit, the MC9S12P128 . Since the T64 has different mask sets and different register locations and values, I think we cannot reallybe sure of getting a connection with that BDM, with the bundled drivers/SDK. The hit is designed to work with only the parts supplied within the kit is what I feel.

__________________
Sunny.


Guru

Status: Offline
Posts: 2338
Date:

yes of course, but with the kit i can test other bdms if the driver is good and learn to play with locking the chip.



__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 49
Date:

okay, I'm back in to the project yesterday i install malossi 182cc kit but have a issue the motor go down if i accelerate and decelerate fast, if i accelerate and them decelerate slow the engine run fine and stay in idle very nice, i going to see if it is a issue or motor only need run, after that i will continue my tests with bdm etc.


-- Edited by mikaspt on Sunday 26th of September 2010 08:43:54 PM

__________________


Veteran Member

Status: Offline
Posts: 75
Date:

P&E Micro BDM should work fine with the chip to erase and unsecure it, i purchased a generic BDM once to reflash MS2 chips that were damaged and was unable to unsecure and flash them with the generic BDM.

I bought another new BDM multilink from P&E and all is fine again.

The P&E will work fine with the free version of CodeWorrior but CW free has a 64K limit on code .

__________________


Guru

Status: Offline
Posts: 2338
Date:

How about P&E flashing software, I recall the price of that being around 400usd + 100usd for the interface. Additional software may be needed as codewarrior is not so good to read the firmware out of the chip - or ?

For generic flashing purposes we really need a low cost device too...


__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 75
Date:

PetriK wrote:

How about P&E flashing software, I recall the price of that being around 400usd + 100usd for the interface. Additional software may be needed as codewarrior is not so good to read the firmware out of the chip - or ?

For generic flashing purposes we really need a low cost device too...



Not sure, i use CW to reflash the serial monitor back on the chip with the BDM , so all i do is erase the chip and load the monitor.

Now i do know i can load a S19 that is under 64K on the chip through CW with the P&E BDM with no problems.

 



__________________


Veteran Member

Status: Offline
Posts: 68
Date:

BUMP!

So what is everyone up to? Any progress or further findings so far?

__________________
Sunny.


Guru

Status: Offline
Posts: 2338
Date:

waiting for the interface - and guess what, today i received a note which said its been returned to freescale. I guess they had not noted my customs clearance email sent to them a week ago.


__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Veteran Member

Status: Offline
Posts: 68
Date:

That's so sad! Does this mean you'll have to pay for the shipping again? Looks like Finland has some pretty tight customs rules! Don't know how many more days it's going to take for the re-shipping to be completed..let's just hope for the best!

__________________
Sunny.


Member

Status: Offline
Posts: 19
Date:

No more information except waiting for this interface.
If it doesn't work then we'll try to find another way!
There is not much I can do at the moment.

I have a contact in my town who knows people that do hacking of car ECU... I haven't met him yet, but perharps they may help us.

__________________


Guru

Status: Offline
Posts: 2338
Date:

Well like said many times earlier - I suspect to have a driver issue with the BDM interface(s) I have.

Anyone is free to suggest how to install a working USB BDM Windows driver package. After 1 hour of searching in the internet could not find one that would work.

I can find codewarrior TBDML file, but for hcs12mem we need a different driver which I was unable to locate.

Device is e.g.
JB16-JMxx USBDM (TBDML mode)



-- Edited by PetriK on Sunday 3rd of October 2010 09:15:13 AM

__________________

When asking a question, you can also consider posting it to facebook:

http://www.facebook.com/ecueditorcom



Member

Status: Offline
Posts: 19
Date:

Ok I'm sorry, but I need a clear status.
BDM device: JB16-JMxx USBDM
What is the software you are using? And the driver (driver package), where it comes from?

One idea: try do use a libusb based driver to developp our own software tool. I have already done that with a Xilinx USB Cable. But that's may be more complicated than helpfull.
Check this: http://usbdm.sourceforge.net/USBDM_V4.0/USBDM_FlashProgrammers/html/index.html
This app is libusb based. Libusb is a kind of generic driver. You can send USB packets through any device you want (that's the complicated part, because you have to make some reverse enginering in order to get the device understanding what you are sending).


Do you have a clear idea why you think this is the driver?
Check this application also (I don't clearly get what you have already tried, sorry if you have already test it): http://sourceforge.net/projects/hcs12mem/



__________________
«First  <  1 2 3 4 5 6  >  Last»  | Page of 6  sorted by
 
Quick Reply

Please log in to post quick replies.

Tweet this page Post to Digg Post to Del.icio.us


Create your own FREE Forum
Report Abuse
Powered by ActiveBoard