UDS is a high level diagnostic protocol, it needs to ride on a network later. UDS is an ISO standard, it’s not published publicly you’d have to buy the document, but there is plenty of information to be found online second hand so I didn’t need the doc and you likely won’t either. How that process of calculating the keys works, size of the keys, what security level gives access to what…those things are all specific to each auto manufacturer For example seed/key authentication, UDS just provides for security levels and a mechanism to exchange a seed and key. However UDS is specifically designed for manufacturers to have lots of flexibility in their products implementations, so you will need to learn the process specific to the ECU you are working with. UDS is great as it’s a standard so there is a lot that is going to be common across ECUs that support it. If you can observe an existing tool, via capturing communications, that’s the ideal way to learn how the process goes. I learned this process, in order to create my own software that can flash an ECU. If you want to upload a modified firmware, do you need to erase the memory and request a flash and address range? Once you get in programming mode, how do you manage to ask the ECU for the correct file? Is it necessary to specify an address region? Are the UDS sequence somehow general for any brand or does it changes? If it does, is there any documentation about specific brands? Once you enter the key successfully you can get it to programming modeīesides that, I'm full-blank about the process, any help will be highly appreciated. There's a UDS sequence that must be followed to get the ECU in programming modeĪ process inside the UDS sequence requires a security key exchange (seed/key algo must be found or brute force access) I've been doing my research the past few days but find it difficult, as far as I'm aware this is what I got If I'm wrong, please correct me): Thanks given by: vanos batam, charlesroy88, sidj, Marcos, teris, CLK1201, nadim malouf, rabihfiras, mardoc, fixitman, sam pro, rico126, daro_mayday, clevo, lolo2020, maaxxyy, letnI, AutoTech81, Camautorepair, r66r66, jakesman, jull, mhhtech, voxsam, Roturbo, jmechanic, Mr.Tester, BMWMDS, automac, BimmerGT1, nedved59, madinina84, herfemp, chulin, Shokunin, sr22vet, julespatch, makura, Damex33, boetvisagie, germtech, Parrafin23, kelrich7, dannygn, talyerinc, Tech61, leona-lvov, andreu22, CEworkshop, Nguyenquanglam, narkeleptk, Fil023, luco7, alex5012, jakycar, roma5000, The Gig, yjkuio, audiserg, doslamer, tkinyan, kila, boy_n, rgp16, Vines, domel45, BMW LEARNING, tttttttttt, Gringo, plasticman1971, amaflo, Tpauto, Rachon, adlr, jinshun123, tortu25, wattios, antal, dtallant77, antonypaul, acent, hisoysal, Mercenaru, bmw325, volthz, herly, ibi, dany72, fifegt, j4ru, efrairo, iDIDNTdoIT, tou2ni, lDim, volvistas, eltoro888, lobo2000, gezame, Injeprog, Taki_da, leminhautotek, yoyomartin2003, chriskain, wecki2, aristos, KoDFeniks, trucker905, zalimhan74, checka, dolphin123, juan1010102001, knuffe47, sebadium, autofault, brghtwll, MUFC, Sergey.I'm looking for learning resources about the topic, this is a personal project and want to learn and understand how flashing tools work, looking to work with a Hitachi SH705X (read, write, checksum calc), any advice, learning resources, or orientation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |