Announcement

Collapse
No announcement yet.

Flashing the MK60 with ZCP software

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Originally posted by Bry5on View Post

    Looks like only the MS43 transmits it on 0x338 (DME3), Byte 2

    (STATE_SOF_CAN):
    • 0 = Sport On (requested by SMG)
    • 1 = Sport Off
    • 2 = Sport On
    • 3 = Error
    ​
    We could add it to the 0401 MSS54HP thanks to karter16 ..

    The more I think about this, the more I like it more than memory. The sport button would finally have a real useful purpose.
    DME3 is not present with MS43 except on the Alpina Roadsters MS430070 firmware. However... We have a Spare input with pullup resistor already in place, so we could easily add that in the code. Even though i don't know what to do with it since Im not a friend of map switching or pops and bangs.

    DSC being stand alone controllable would be my prefered way though.

    As soon as you have a way to dump the firmware more easily, i can call a friend with an MK MK60.

    Comment


      Originally posted by sda2 View Post
      As soon as you have a way to dump the firmware more easily, i can call a friend with an MK MK60.
      Hell yeah! That would be awesome.

      Also, I put Bry5on's non-ZCP M3 module dump through the robot disassembly workflow. It's even more similar to the ZCP image than the non-M image is (no surprise there).

      The non-ZCP image is genuinely missing the M track mode button handler, just like the non-M image is. So a FW reflash is required to use this extra input.

      Other differences include a temperature-aware pressure scaler for the pump on the ZCP and differences in the maps. I haven't dug into the maps to know exactly what changes, but they are different.

      Super dense, LLM-speak analysis in https://github.com/heinzboehmer/MK60...differences.md
      2002 Topasblau M3 - Coupe - 6MT - Karbonius CSL Airbox - SSV1 - HJS - Mullet Tune - MK60 Swap - E86 Front Triangulation - ZCP Rack - Nogaros - AutoSolutions - 996 Brembos - Slon - CMP - VinceBar - Koni - Eibach - BlueBus - Journal

      2012 Alpinweiss 128i - Coupe - 6AT - Slicktop - Manual Seats - Daily - Journal

      Comment


        Originally posted by heinzboehmer View Post

        Hell yeah! That would be awesome.

        Also, I put Bry5on's non-ZCP M3 module dump through the robot disassembly workflow. It's even more similar to the ZCP image than the non-M image is (no surprise there).

        The non-ZCP image is genuinely missing the M track mode button handler, just like the non-M image is. So a FW reflash is required to use this extra input.

        Other differences include a temperature-aware pressure scaler for the pump on the ZCP and differences in the maps. I haven't dug into the maps to know exactly what changes, but they are different.

        Super dense, LLM-speak analysis in https://github.com/heinzboehmer/MK60...differences.md
        Is that dump 813.3 or 818.3?

        Comment


          Originally posted by terra View Post
          Is that dump 813.3 or 818.3?
          Bry5on to confirm, but I think 818.3
          2002 Topasblau M3 - Coupe - 6MT - Karbonius CSL Airbox - SSV1 - HJS - Mullet Tune - MK60 Swap - E86 Front Triangulation - ZCP Rack - Nogaros - AutoSolutions - 996 Brembos - Slon - CMP - VinceBar - Koni - Eibach - BlueBus - Journal

          2012 Alpinweiss 128i - Coupe - 6AT - Slicktop - Manual Seats - Daily - Journal

          Comment


            Originally posted by heinzboehmer View Post

            Bry5on to confirm, but I think 818.3
            It’s not the fancy one.
            ‘02 332iT / 6 | ‘70 Jaguar XJ6 electric conversion

            Comment


              So re: flashable modules -- in the past I have been told "ID_HW_NR" (from the 'ident' job --output reproduced below) being 0.0 indicates a flashable module while 0.1 indicates not-flashable (i.e fixed rom). Anything in the disassembly to indicate that could be a real marker of onboard flash vs ROM?

              Code:
               JOB_STATUS = OKAY
              
              ID_BMW_NR = 2282250
              
              [B]ID_HW_NR = 0.1[/B]
              
              ID_COD_INDEX = 6 00 06 ..
              
              ID_DIAG_INDEX = 6 00 06 ..
              
              ID_VAR_INDEX = 22 00 16 ..
              
              ID_DATUM_JAHR = 2004 07 D4 .Ô
              
              ID_DATUM_MONAT = 9 00 09 ..
              
              ID_DATUM_TAG = 11 00 0B ..
              
              ID_DATUM = 11.09.2004
              
              ID_LIEF_NR = 24 00 18 ..
              
              ID_LIEF_TEXT = Temic
              
              ID_SW_NR_FSV = 0.0.129
              
              ID_SW_NR_OSV = 0.0.0
              
              ID_SW_NR_MCV = 0.0.0
              
              ID_SW_NR_RES = 0.0.0
              
              _TEL_AUFTRAG = 6 Bytes
              
              0000 : B8 29 F1 02 1A 80 ¸)ñ..?
              
              _TEL_ANTWORT = 36 Bytes
              
              0000 : B8 F1 29 1F 5A 80 00 00 02 28 22 50 [B]01 [/B]06 00 06 ¸ñ).Z?.. .("P....
              
              0020 : 00 00 00 73 ...s
              ​

              Comment


                Originally posted by terra View Post
                So re: flashable modules -- in the past I have been told "ID_HW_NR" (from the 'ident' job --output reproduced below) being 0.0 indicates a flashable module while 0.1 indicates not-flashable (i.e fixed rom). Anything in the disassembly to indicate that could be a real marker of onboard flash vs ROM?
                I've seen no routines that read/write the FW itself on any of the E46 modules (except for in the manufacturer diag protocol). There are EEPROM read/write routines present, though. I'd have to go double check, but I think all the EEPROM logic is identical across modules.

                Long story short, there isn't anything I've seen in the FW to indicate whether the claim is true or not.

                I do have both supposedly non-flashable and supposedly flashable modules here with me, so let me see what the ident job says for both.
                2002 Topasblau M3 - Coupe - 6MT - Karbonius CSL Airbox - SSV1 - HJS - Mullet Tune - MK60 Swap - E86 Front Triangulation - ZCP Rack - Nogaros - AutoSolutions - 996 Brembos - Slon - CMP - VinceBar - Koni - Eibach - BlueBus - Journal

                2012 Alpinweiss 128i - Coupe - 6AT - Slicktop - Manual Seats - Daily - Journal

                Comment


                  820.3:

                  Code:
                    JOB_STATUS                      = OKAY
                  
                    ID_BMW_NR                       = 6765452
                  
                    ID_HW_NR                        = 0.1
                  
                    ...
                  ​

                  817.3:

                  Code:
                    JOB_STATUS                      = OKAY
                  
                    ID_BMW_NR                       = 2282420
                  
                    ID_HW_NR                        = 0.0
                  
                    ...
                  ​

                  So it lines up with that claim, if it turns out that the 820.3 isn't flashable.
                  2002 Topasblau M3 - Coupe - 6MT - Karbonius CSL Airbox - SSV1 - HJS - Mullet Tune - MK60 Swap - E86 Front Triangulation - ZCP Rack - Nogaros - AutoSolutions - 996 Brembos - Slon - CMP - VinceBar - Koni - Eibach - BlueBus - Journal

                  2012 Alpinweiss 128i - Coupe - 6AT - Slicktop - Manual Seats - Daily - Journal

                  Comment

                  Working...
                  X