Pages: 1 ... 3 4 [5]
Author Topic: Logging with KWP-2000 protocol  (Read 36960 times)
elRey
Hero Member
*****

Karma: +20/-0
Offline Offline

Posts: 530


« Reply #60 on: May 06, 2017, 08:55:46 PM »

edit: my post may violate license of me7logger. removing it for now.
« Last Edit: May 07, 2017, 04:04:38 PM by elRey » Logged
de_F
Newbie
*

Karma: +8/-0
Offline Offline

Posts: 12


« Reply #61 on: October 31, 2018, 06:42:26 AM »

I'm already using 0x35/0x36, but is there any other way?

It's KWP.


Sorry for resurrecting this old thread,

Service 35 RequestUpload seems to work on MED17 and as long as I aim for an upload within 0x40000h and 0x7FFFF I get my response as requested.

The RAM tables on MED17 for example are possibly located at 0xC0000000 or 0xD0000000 ect (32bit address). according to A2L's floating around.
It looks like the standard KWP protocol can only handle 24bit addresses, so up to 0xFFFFFF.

I understand you got this working kuebk to make your logger over 0x35 RequestUpload / 0x36 TransferData. But for the moment I keep on getting answer 52 canNotUploadFromSpecifiedAddress (so my addressing is definitely wrong as I am aiming for a blocked/protected address)

Any pointers or possibly just a way to calculate address 0xC0000000 so my request passes ?
« Last Edit: November 03, 2018, 01:00:37 PM by de_F » Logged
kuebk
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 24



« Reply #62 on: November 01, 2018, 01:55:36 AM »

Memory regions are covered in detail in A2L.
Logged
de_F
Newbie
*

Karma: +8/-0
Offline Offline

Posts: 12


« Reply #63 on: November 03, 2018, 12:33:46 PM »

Thanks for the heads up. Should work with 0x400000 and 0x500000 then. I'll give it a shot in the next few days.
Logged
Pages: 1 ... 3 4 [5]
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.014 seconds with 17 queries. (Pretty URLs adds 0s, 0q)