Pages: [1]
Author Topic: There a way to offset the hex address in winols?  (Read 5545 times)
NOTORIOUS VR
Administrator
Hero Member
*****

Karma: +58/-7
Offline Offline

Posts: 1056


« on: August 19, 2012, 01:39:43 PM »

Basically I want to make the file look like/start at say 0x80000 instead of 0x0, is there a way to do this?  I've seen some bins (maybe .ols files) that did this. 

I have an A2L that I want to try to use but it's looking for maps in the 0x800000+ ranges.

I've been tinkering for quite a while and can't seem to figure it out, figured maybe someone here went through this as well.

Thanks Smiley
Logged

SCHNELL ENGINEERING BLOG ·  STANDALONE ECUS · TUNING · DYNO · WIRING · PARTS · VEMS
Google Talk: NOTORIOUS.VR
n00bs start here: http://s4wiki.com/wiki/Tuning
userpike
Hero Member
*****

Karma: +22/-1
Offline Offline

Posts: 763


« Reply #1 on: August 19, 2012, 05:01:32 PM »

I think there should be a section on the forum about how to use WinOls and/or Tuner Pro...read my last post on the "only manipulating LAMFA" thread in "Tuning"....I have so many questions about this subject (WinOls/TunerPro). Wish I could help..
Logged
NOTORIOUS VR
Administrator
Hero Member
*****

Karma: +58/-7
Offline Offline

Posts: 1056


« Reply #2 on: August 20, 2012, 06:11:36 AM »

not a bad idea, I will make a request for a Software section
Logged

SCHNELL ENGINEERING BLOG ·  STANDALONE ECUS · TUNING · DYNO · WIRING · PARTS · VEMS
Google Talk: NOTORIOUS.VR
n00bs start here: http://s4wiki.com/wiki/Tuning
NOTORIOUS VR
Administrator
Hero Member
*****

Karma: +58/-7
Offline Offline

Posts: 1056


« Reply #3 on: August 20, 2012, 06:19:14 AM »

FWIW, I just found where to do it.

Project: Properties > ... Elements (under ECU box) > change display offset to what you want
Logged

SCHNELL ENGINEERING BLOG ·  STANDALONE ECUS · TUNING · DYNO · WIRING · PARTS · VEMS
Google Talk: NOTORIOUS.VR
n00bs start here: http://s4wiki.com/wiki/Tuning
Pages: [1]
  Print  
 
Jump to:  

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