+- CarTechnoloGY (https://cartechnology.co.uk)
+-- Forum: Discussions All about Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=310)
+--- Forum: Automotive Help & Discussions / Software and Hardware (https://cartechnology.co.uk/forumdisplay.php?fid=40)
+---- Forum: BMW - Mini - Rolls Royce (https://cartechnology.co.uk/forumdisplay.php?fid=61)
+---- Thread: Changing adjustblock (/showthread.php?tid=59517)
Changing adjustblock - alexnaoumov - 22-01-2022
Hey friends,
I have bought used evo that is messed up. It has SDARS in the Adjustblock but physically has DAB and that kind of stuff. Also wrong DVD player in the adjustblock and probably that's why I can't flash 271a on it.
I dont care a lot if I break it at this point, main goal is that I want to try to change adjustblock, learn from it and run the patch for black screen after that.
However I dont succeed doing this at this point because it says invalid ID.. Who can tell me what the right syntax is for the seta command?
Code:
hu-omap:/dev/shmem> sysetshellevo --connect
#HW: nbt
#CONNECTED
#STATE: FullyOperable
syset:>geta E2P.ProdLogistic.HWCoding.DMB
NAME: E2P.ProdLogistic.HWCoding.DMB
TYPE: UInt8
ID: 0x80150001
MODIF: OK
SIZE: 0x01
VALUE: 0x00
syset:>seta E2P.ProdLogistic.HWCoding.DMB=0x04
#SET RESULT: Invalid id
syset:>seta E2P.ProdLogistic.HWCoding.DMB=04
#SET RESULT: Invalid id
syset:>seta E2P.ProdLogistic.HWCoding.DMB 0x04
#SET RESULT: Invalid id
syset:>seta 0x80150001=0x04
#SET RESULT: Invalid id
syset:>RE: Changing adjustblock - m5proud - 26-01-2022
Z-modem to download, then edit it and upload back. And what about black screen patch?
RE: Changing adjustblock - RomeyRome - 15-01-2023
(26-01-2022, 16:40 PM)m5proud Wrote: Z-modem to download, then edit it and upload back. And what about black screen patch?
How do you mean? Only copy I can find of it is in /dev/shmem/sysetpage, and that looks like it's a cached copy.
RE: Changing adjustblock - donjuan020 - 16-01-2023
(22-01-2022, 00:39 AM)alexnaoumov Wrote: Hey friends,it happened to me before. we solved this problem with scp.
I have bought used evo that is messed up. It has SDARS in the Adjustblock but physically has DAB and that kind of stuff. Also wrong DVD player in the adjustblock and probably that's why I can't flash 271a on it.
I dont care a lot if I break it at this point, main goal is that I want to try to change adjustblock, learn from it and run the patch for black screen after that.
However I dont succeed doing this at this point because it says invalid ID.. Who can tell me what the right syntax is for the seta command?
I added the current adjustblock as text dump in attachments. As you can see it's completely wrong because this is European HW 4.1 with DAB, also proddate is in 2018 and not in 2015..Code:hu-omap:/dev/shmem> sysetshellevo --connect
#HW: nbt
#CONNECTED
#STATE: FullyOperable
syset:>geta E2P.ProdLogistic.HWCoding.DMB
NAME: E2P.ProdLogistic.HWCoding.DMB
TYPE: UInt8
ID: 0x80150001
MODIF: OK
SIZE: 0x01
VALUE: 0x00
syset:>seta E2P.ProdLogistic.HWCoding.DMB=0x04
#SET RESULT: Invalid id
syset:>seta E2P.ProdLogistic.HWCoding.DMB=04
#SET RESULT: Invalid id
syset:>seta E2P.ProdLogistic.HWCoding.DMB 0x04
#SET RESULT: Invalid id
syset:>seta 0x80150001=0x04
#SET RESULT: Invalid id
syset:>
RE: Changing adjustblock - walkernight88 - 16-01-2023
(15-01-2023, 09:57 AM)RomeyRome Wrote:(26-01-2022, 16:40 PM)m5proud Wrote: Z-modem to download, then edit it and upload back. And what about black screen patch?
How do you mean? Only copy I can find of it is in /dev/shmem/sysetpage, and that looks like it's a cached copy.
Well to download and upload the binary from headunit. I prefer to add the scp to headunit. After you can update the adjustblock using the commands on the evo. It's not "a file", it's in 850... What you see in sysetpage it's exactly as you described, a cache file. I don't know if all the utilities on evo are calculating the checksum or not. So might be a good idea to calculate the checksum in advance when you edit the binary.
RE: Changing adjustblock - RomeyRome - 17-01-2023
(16-01-2023, 13:29 PM)walkernight88 Wrote:(15-01-2023, 09:57 AM)RomeyRome Wrote:(26-01-2022, 16:40 PM)m5proud Wrote: Z-modem to download, then edit it and upload back. And what about black screen patch?
How do you mean? Only copy I can find of it is in /dev/shmem/sysetpage, and that looks like it's a cached copy.
Well to download and upload the binary from headunit. I prefer to add the scp to headunit. After you can update the adjustblock using the commands on the evo. It's not "a file", it's in 850... What you see in sysetpage it's exactly as you described, a cache file. I don't know if all the utilities on evo are calculating the checksum or not. So might be a good idea to calculate the checksum in advance when you edit the binary.
Thank you for the hints. I have no problem copying files to and from the unit via usb, nfs, cifs, or whatever.
I figured at this point that adjustblock isn't just a file, so it must device pointer somewhere. like adjinfo tries to read from /dev/fs0 by default, but it's obviously not there. sysetshellevo and sysetadjread both seem to read off the cached sysetpage, becuase they stop showing the right values (everything 0xFF or 0x00) when you delete sysetpage.... so idk
RE: Changing adjustblock - RuleNormaliai - 17-01-2023
well, i can't share how it's done, as this forum lately is not about sharing information anymore, but if someone really needs it i can help with changing adj.
RE: Changing adjustblock - sameur10 - 17-01-2023
Hi
how u can extract adjustblock ? here u go
extract sysetV850io and copy sysetV850io to unit
Chmod with 755
then type this command :
./sysetV850io --ipc=/net/hu-jacinto/dev/ipc/ipc10 --dump --adjust
it will create a file sysetV850io_dump_adjust_0_xxxxxx...bin , enjoy
RE: Changing adjustblock - RomeyRome - 17-01-2023
(17-01-2023, 17:49 PM)sameur10 Wrote: Hi
how u can extract adjustblock ? here u go
extract sysetV850io and copy sysetV850io to unit
Chmod with 755
then type this command :
./sysetV850io --ipc=/net/hu-jacinto/dev/ipc/ipc10 --dump --adjust
it will create a file sysetV850io_dump_adjust_0_xxxxxx...bin , enjoy
Thank you! Very helpful.
I guess the next obvious question is - how do you write it back? --erase and --load error out with cbErrno: 15
RE: Changing adjustblock - zero9 - 17-01-2023
Code:
Mandatory non-exclusive options:
--ipc Defines IPC device full path id. Usage example:
a) --ipc=/dev/ipc/ipc10 for real IPC device id
b) --ipc=simu:/var/fifo1;/var/fifo2 for IPC simulation mode using FIFO
Mandatory mutually exclusive options:
Actions section:
--append Defines append action. Must not have option value. Valid only for --flash partition type.
--erase Defines erase action. Must not have option value. Valid for any partition type.
--load Defines loading from file and writing to partition action. Valid for any partition type.
Requires --path option value to be passed.
--dump Defines reading from partition and dumping to file action. Valid for any partition type.
Requires --path option value to be passed.
--stinfo Defines storage info getting, printing and dumping to file as binary action.
Requires --path option value to be passed.
No option from partition types section can be used with this option.
Partition types section:
--flash Defines action on FLASH partition.
Cannot be used with neither --load nor --stinfo option.
If used without --partindex option partition index set to Zero by default.
--eeprom Defines action on EEPROM partition.
Cannot be used with neither --append nor --stinfo option.
If used without --partindex option partition index set to Zero by default.
--adjust Defines action on ADJUST block.
Cannot be used with neither --append nor --stinfo option.
If used without --partindex option partition index set to Zero by default.
Mandatory action specific options:
--path Specifies full path to file handled as source or destination
depending on given action. Must have option value.
Valid only for --append, --load, --dump, --stinfo.
For --append, --load this option is mandatory. For the rest of actions
if option not given, unique file path is generated in the following
format according to action type:
a) "sysetV850io_{0}_{1}_{2}_{3}.bin" - for --dump action
where {0} - action type symbolic interpretation,
{1} - partition type symbolic interpretation,
{2} - partition index symbolic interpretation,
{3} - unique time stamp symbolic interpretation;
b) "sysetV850io_stinfo_{0}.bin" - for --stinfo action
where {0} - unique time stamp symbolic interpretation.