+- 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: NBT Evo HW 4.1 flashing gives SA_SK negative response (/showthread.php?tid=68152)
NBT Evo HW 4.1 flashing gives SA_SK negative response - RomeyRome - 24-08-2022
Part #65128708269
Sitting on a bench.
Comes in several g-series (and f90), 03/18 and up. Goal is to put it into an F02.
V580 cleared. boot-loader functional. Can ssh in and "do stuff". Switch between bootloader mode & app mode, copy files over the network, etc.
Trying to flash it to 1803 (for apix1 screen support) results in following error.
Code:
TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2022/08/23-17:57:02.200
[] prepareTALExecution started
[] prepareTALExecution finished
[] prepareVehicleForFlash started
MCDDiagService<id=20600, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=CC, description=error: negative response : conditionsNotCorrect, link=#RtGen_MultipleEcuJob_LogicalLink>
MCDDiagService<id=38000, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=RC_CPPC, description=ECU signaled that any ProgrammingPreCondition not fullfilled, but no further details provided from ECU!, link=HU_NBT2_63_ETHERNET>
[] prepareVehicleForFlash finished
[HU_NBT2 - 63] prepareECUforBLUpdate started
[HU_NBT2 - 63] prepareECUforBLUpdate finished
[HU_NBT2 - 63] authenticateECUforBLUpdate started
MCDDiagService<id=16616, job=com.bmw.psdz.jobs.uds.MCD3_AuthenticateECUforBLUpdate, service=SA_SK - SecurityAccessSendKey, description=error: negative response : generalReject, link=HU_NBT2_63_ETHERNET>
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files.
[HU_NBT2 - 63] installECUBL started
[HU_NBT2 - 63] installECUBL finished
[HU_NBT2 - 63] finalizeECUBLUpdate started
[HU_NBT2 - 63] finalizeECUBLUpdate finished
[] finalizeVehicleFlash started
MCDDiagService<id=230600, job=com.bmw.psdz.jobs.common.MCD3_FinalizeVehicleFlash, service=DSC, description=error: negative response : conditionsNotCorrect, link=#RtGen_MultipleEcuJob_LogicalLink>
[] finalizeVehicleFlash finished
[] finalizeTALExecution started
[] finalizeTALExecution finished
TAL execution finished
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "5min 30s". [C206]Tried ENET & I COM. With & without gateway (8sk). Without gateway fails looking for a gateway.
Tried with Evo connected to gateway and directly to switch.
UDS or IP doesn't matter. Though over IP it gives a "timeout" rather than negative response.
I don't know what's on the screen because I only have an apix1 screen with a voltage converter & it just says "No Signal"
Esys screenshots attached of before & after calc.
I have tried various G & F series FAs, including the original one built from the VIN, But have not gotten any further.
Thoughts?
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - flashxcode - 24-08-2022
Share the tal. I can have a look on it
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - RomeyRome - 24-08-2022
(24-08-2022, 18:21 PM)flashxcode Wrote: Share the tal. I can have a look on itHere are two. One as generated, and one I end up using after I strip all the other ECUs out.
Thank you.
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - Jartsa - 25-08-2022
I have similar problem on one F10 B%O amplifier.
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - flashxcode - 25-08-2022
(24-08-2022, 19:57 PM)RomeyRome Wrote:(24-08-2022, 18:21 PM)flashxcode Wrote: Share the tal. I can have a look on itHere are two. One as generated, and one I end up using after I strip all the other ECUs out.
Thank you.
Here you are.
Load this tal, check only blFlash and swDeploy and start it
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - RomeyRome - 27-08-2022
(25-08-2022, 06:12 AM) flashxcode Wrote:(24-08-2022, 19:57 PM)RomeyRome Wrote:(24-08-2022, 18:21 PM)flashxcode Wrote: Share the tal. I can have a look on itHere are two. One as generated, and one I end up using after I strip all the other ECUs out.
Thank you.
Here you are.
Load this tal, check only blFlash and swDeploy and start it
Thank you for your effort, but pretty much the same result. generalReject with UDS or timeout with http method.
ESys 3.30.1, if that matters.
Unit reboots a few times during the following steps (as it did before):
prepareTALExecution started
prepareVehicleForFlash started
authenticateECUforBLUpdate started
Code:
Read SVT before TAL execution started.
TAL execution started.
VCM Update: VCM-Update is deactivated. VCM will not be updated. [C197]
ExecutionID=2022/08/26-13:23:22.425
[] prepareTALExecution started [PROGRESS]
[] prepareTALExecution finished [PROGRESS]
[] prepareVehicleForFlash started [PROGRESS]
MCDDiagService<id=20600, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=CC, description=error: negative response : conditionsNotCorrect, link=#RtGen_MultipleEcuJob_LogicalLink> [DIAGSERVICE]
MCDDiagService<id=38000, job=com.bmw.psdz.jobs.common.MCD3_PrepareVehicleForFlash, service=RC_CPPC, description=ECU signaled that any ProgrammingPreCondition not fullfilled, but no further details provided from ECU!, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] prepareVehicleForFlash finished [PROGRESS]
[HU_NBT2 - 63] prepareECUforBLUpdate started [PROGRESS]
[HU_NBT2 - 63] prepareECUforBLUpdate finished [PROGRESS]
[HU_NBT2 - 63] authenticateECUforBLUpdate started [PROGRESS]
MCDDiagService<id=16616, job=com.bmw.psdz.jobs.uds.MCD3_AuthenticateECUforBLUpdate, service=SA_SK - SecurityAccessSendKey, description=error: negative response : generalReject, link=HU_NBT2_63_ETHERNET> [DIAGSERVICE]
[] job failed with negative response error:
code: cancel ecu requires finalize
description: Service SA_SK returned a negative response with response code generalReject; LinkName: HU_NBT2_63_ETHERNET
severity: ERROR
[THROWABLE]
[HU_NBT2 - 63] There was an error during TAL execution, please check the log files. [WARN]
[HU_NBT2 - 63] installECUBL started [PROGRESS]
[HU_NBT2 - 63] installECUBL finished [PROGRESS]
[HU_NBT2 - 63] finalizeECUBLUpdate started [PROGRESS]
[HU_NBT2 - 63] finalizeECUBLUpdate finished [PROGRESS]
[] finalizeVehicleFlash started [PROGRESS]
[] finalizeVehicleFlash finished [PROGRESS]
[] finalizeTALExecution started [PROGRESS]
[] finalizeTALExecution finished [PROGRESS]
TAL execution finished [TAL_EXECUTION_FINISHED]
TAL-Execution finished with status: "FinishedWithError". [C207]
TAL execution finished. Duration: "5min 10s". [C206]
Read SVT after TAL execution started.
Read SVT after TAL execution finished.It's almost as if it's trying to reach out to a service that is not running on the evo unit.
List of running procs in the bootloader, if it matters.
Code:
pid Arguments
1 procnto-instr -v -mLr~i -F1500
2 slogger -m -u 110 -s 256k
3 devc-seromap -e -F -b115200 -c48000000/16 0x48020000^2,72
4100 starter -u -s -e -g -vvv -p 30 -S libnbt_starter_plugin-jacinto.so -O verbose=3,transferverbose=3 -c /etc/starter.cfg
4101 /bin/pipe
4102 /bin/pci-j5 -gen1
4103 /bin/dev-sysregs2 -c /etc/sysregs.cfg
4104 /bin/dev-i2c -djacinto5 -C/etc/i2c.cfg
4105 /bin/io-pkt-v4 -S -ptcpip stacksize=8192,enmap=0
4106 /bin/servicebroker -i1001 -m/net/hu-omap/srv/servicebroker -q160.48.199.254:3746 -f/etc/servicebroker.cfg
4107 /bin/dev-InicServer -c/etc/dev-InicServer-nbtevo.cfg -p63
4108 /bin/HUJacintoStage1 --mode=bolo --activecomponents=onoff,env,most,persistency --dsiwaitforboot=1 --devmode=master --inicClockMode=slave --dsiforcetcp=1 --mlbCfgFile=/etc/dev-InicServer-nbtevo.cfg --mapMOSTSubSystem.DSYSMOSTServer=MOSTSubSystemServer.DSYSMOSTServer --mapMOSTSubSystem.DSYSNetworkManagement=MOSTSubSystemServer.DSYSNetworkManagement --mapPersistency.DSYSPersistencyFsc=PersistencyJacinto.DSYSPersistencyFsc --mapPersistency.DSYSPersistencyAdmin=PersistencyJacinto.DSYSPersistencyAdmin --mapPersistency.DSYSErrorMemoryAppClient=PersistencyJacinto.DSYSErrorMemoryAppClient --enAEH1 --reclaim_normal=100,16 --reclaim_eager=20,16,5s --reclaim_lazy=150,48 --i=dm0 --diag=DIAGADR63 --eal-debug --trccachesize=10000 --trcringbuf --buffsize=10 --bp=/etc --SBWaitTime=50 --heartbeat-interval=2
4109 devf-generic -x1 -r -b5 -s0x08000000,128M
4110 /bin/io-ipc -vvvvv -c /etc/io-ipc-v2-j5-bolo.cfg
4111 /bin/dev-spi-dra6xx -c /etc/spi1-apix1.cfg
4112 /bin/dev-spi-dra6xx -c /etc/spi0.cfg
8211 /bin/dev-eth-ctrl -c /etc/ethctrl.cfg
16401 /bin/autoarpd -i vlan73 -a 239.192.255.251 -p 30490
16406 /bin/someip_sddaemon -c /etc/someip/someip.conf
28692 /bin/random -p -t
32786 /bin/watchdog5-jacinto -s smon=HBWATCHDOG2 -t prio=30,timeout=10
32792 /bin/dumper -m -w -d /net/hu-omap/fs/sda1/dump/jacinto
32793 /bin/NBTPathology -P_low=10 -P_high=17 --pollQNET 3000 --qnet_actions=252926 --trccachesize=500 --trcringbuf --buffsize=10 --bp=/etc --bp=/var/opt/car --trace-startup-delay=5000 --heartbeat-interval=2 --mapSystemInformation.DSYSVersionInfoClient=SystemInformation_jacinto.DSYSVersionInfoClient --mapWatchdogHandler.DSYSNBTPathologyVictim=WatchdogHandler_jacinto.DSYSNBTPathologyVictim --mapWatchdogHandler.DSYSErrorMemoryAppClient=WatchdogHandler_jacinto.DSYSErrorMemoryAppClient --mapPowerStateController.DSYSNBTLifecycleInfo=PowerStateControllerJacinto.DSYSNBTLifecycleInfo --phogs_threshold=30 --phogs_interval=50 --saveFilesOnHD
40981 /bin/dumper -z1 -w -d /var/opt/car/pathology
40983 /bin/LogisticHUJacintoStage --activecomponents=logistic,ethernet_diagnostics --trccachesize=1500 --trcringbuf --buffsize=10 --bp=/etc --bp=/var/opt/sys --trace-startup-delay=4000 --conf 0xF0002000 0xF0002001 0xF0002002 0xF0002003 0xF0002004 0xF0002005 0xF0002006 0xF0002007 0xF0002008 0xF000200A 0xF000201A --heartbeat-interval=2 --mapMOSTSubSystem.DSYSMOSTServer=MOSTSubSystemServer.DSYSMOSTServer
40986 /bin/NbtEvoJacintoDiagHUHighApp --operationmode=bootloader --bootloader --configuration=/etc/errormemory.bin --trccachesize=2500 --trcringbuf --buffsize=10 --bp=/etc --bp=/var/opt/sys --heartbeat-interval=2 --mapMOSTSubSystem.DSYSMOSTServer=MOSTSubSystemServer.DSYSMOSTServer --mapEthernetDiagnosticsMaster.DCARNBTDevEthDiag=EthernetDiagnosticsMasterHU.DCARNBTDevEthDiag --mapTrustedVIN.DCARTrustedVINController=TrustedVIN.DCORETrustedVINController
40988 /bin/sysetsrvproxyevo_s --vv --syset-initstate=F --syset-nodtc --trccachesize=2500 --trcringbuf --buffsize=10 --bp=/etc --bp=/var/opt/sys --trace-startup-delay=4000 --dsiwaitforboot=1 --dsiusetcp=0 --heartbeat-interval=2
40989 /bin/SwdlSlave --trccachesize=1000 --trcringbuf --buffsize=10 --bp=/etc --bp=/var/opt/sys --heartbeat-interval=2
40991 /bin/devc-seromap -u4 -e -F -b115200 -c48000000/16 0x481AA000^2,46
40992 /bin/devc-pty
45086 /opt/sys/bin/srm -t -c /var/opt/sys
45089 /bin/dev-spi-dra6xx -c /etc/spi2_saturn_hd_bolo.cfg
45090 /bin/devc-seromap -u2 -e -F -b115200 -c48000000/16 0x48024000^2,74
45091 /bin/multicored -d /dev/null -m/hbsystem/multicore -N -n6000 -B3000 -t40 -D2 -F0 -C/etc/dnid.rc
45093 /opt/sys/bin/devc-sernuke -u5 -E -F -b921600 -c48000000/13 0x481A6000^2,44
45094 /bin/inetd /etc/inetd.conf
49188 /bin/ksh /opt/car/bin/serialport_listen.sh
57383 cat /dev/ser5
65563 ksh ksh
73768 sshd -i
77865 -ksh
98346 /opt/os/bin/qconn
98347 /opt/sys/bin/qnxcommd
98348 /opt/os/bin/io-usb -ddm816x-mg ioport=0x47401c00,irq=19
98349 /opt/sys/bin/vdev-medialaunch -z -f /opt/sys/etc/umass-enum.cfg -C -H hub_detect,maxhubs=4 -d1RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - Maxx18771 - 27-08-2022
First problem the unit is for USA market, if you check the rear of the unit there is a pink connector over the fm's antennas (Black and withe connectors).
Second problem the f02 is build from 2008 to 2015, i think you can't find swfl in psdzdata...
My suggestion is to flash unit in most similar Bmw to f02 and then change the Bhauart in fdl.
Max
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - RomeyRome - 27-08-2022
(27-08-2022, 04:59 AM)Maxx18771 Wrote: First problem the unit is for USA market, if you check the rear of the unit there is a pink connector over the fm's antennas (Black and withe connectors).
Second problem the f02 is build from 2008 to 2015, i think you can't find swfl in psdzdata...
My suggestion is to flash unit in most similar Bmw to f02 and then change the Bhauart in fdl.
Max
Well, I'm in the US, so I want US market.
I'm flashing it with a G12 FA. F90 would be the closest to f02 I think. But I have tried a good variety of FAs.I haven't tried is newer istep than 18-03 though.
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - dasi - 27-08-2022
(27-08-2022, 05:37 AM)RomeyRome Wrote:(27-08-2022, 04:59 AM)Maxx18771 Wrote: First problem the unit is for USA market, if you check the rear of the unit there is a pink connector over the fm's antennas (Black and withe connectors).
Second problem the f02 is build from 2008 to 2015, i think you can't find swfl in psdzdata...
My suggestion is to flash unit in most similar Bmw to f02 and then change the Bhauart in fdl.
Max
Well, I'm in the US, so I want US market.
I'm flashing it with a G12 FA. F90 would be the closest to f02 I think. But I have tried a good variety of FAs.I haven't tried is newer istep than 18-03 though.
FA doesn't matter for flashing...
RE: NBT Evo HW 4.1 flashing gives SA_SK negative response - RomeyRome - 22-09-2022
(25-08-2022, 06:12 AM)flashxcode Wrote:(24-08-2022, 19:57 PM)RomeyRome Wrote:(24-08-2022, 18:21 PM)flashxcode Wrote: Share the tal. I can have a look on itHere are two. One as generated, and one I end up using after I strip all the other ECUs out.
Thank you.
Here you are.
Load this tal, check only blFlash and swDeploy and start it
Any other ideas?