rusefi.com

I recently bought a Proteus off ebay to start a project on my Volvo s60. I'm having trouble finding a working release of firmware for this board. Its labeled:
rusEFI Proteus F7
v0.6 march 2021
CPU is STM32F767ZGT6
I attempted using the:
2021 May Proteus QC builds
and i also tried the April build MALBEC rusefi_bundle_proteus_f7.zip

I keep having issues with getting tuner studio to even write any changes when using these firmwares and i keep getting a error referring to the flash.
I've been messing with it for a couple days now and i cant quite figure out if im having a firmware issue/software issue, hardware issue or just my own human error.

Welcome to the forum! Congrats on being first Proteus 0.6 user

Will create a release with proper F7 today and update links to night builds.

Thanks! This will be my first dive into rusEFI . I don't normally make posts but im glad i did because i didn't know i was the first .6 user! Also do you recommend getting a st-link programmer or is the onboard usb adequate?

Onboard USB is perfectly adequate for normal firmware updates.

We now have https://github.com/rusefi/rusefi/releases/tag/2021.05.16_release which supports your chip.

biohazardav wrote: ↑

Sun May 16, 2021 5:26 pm

I recently bought a Proteus off ebay to start a project on my Volvo s60.

What year s60? Any chance you want to start a thread with a picture? Is that a road racing vehicle or else?

So I tried the packages in this picture below: And it gives me this error with either one, also this is the same error that I've gotten with some of the other precompiled bundles. I also noticed that I cant seem to change the tune at all. Any write commands don't seem to work. fault only occurs once I load tunerstudio. It's just a tinker project at the moment but I work at a Volvo dealer and have a s60R that I've been wanting to play with the new dual vvt and DBW and want to see how difficult it would be to build a sort of PNP system that wouldn't require me building another harness but rather just stick with the factory one entirely and if it works well I have a bunch of spare 5 cylinders in their stock form i have been feeling the urge to swap into some older chassis i have laying around.

IF all goes well I might buy a efr7670 and start a build thread on my s60R but currently im helping some locals with some standalones and also finally getting my volvo 240 b234ft build some love .

"QC special build" is failing to communicate "please do not touch me I am special quality control build that's not what real users should be using"

@mck1117 ideas?

https://github.com/rusefi/rusefi/issues/2711 is for the error in the error message which is totally not the root cause of your error

mck1117 this unit was switched to proper nDBANK settings since it has departed with a not failing non-QC snapshot build.

AndreyB wrote: ↑

Sun May 16, 2021 8:57 pm

"QC special build" is failing to communicate "please do not touch me I am special quality control build that's not what real users should be using"

we should put non-consumer builds inside a folder called "special" or something

I agree https://github.com/rusefi/rusefi/issues/2712

FWIW I'm getting the same error.

dbh97 wrote: ↑

Sun May 16, 2021 11:35 pm

FWIW I'm getting the same error.

Neat. I'll give it a try on the F7 0.6 I have here.

Ok, there's a bug in math we use to calculate which flash sector to erase on the 1MB STM32F7 chips. Will have a fix out shortly!

So thats what i originally thought as i saw some communication about that regarding the f7 vs f4 chips but I still lack a lot of understanding of this architecture. That's partly what made me think i needed a st-link programmer because i came across this page looking for key words about this dual bank system?:
https://wiki.segger.com/STM32F7

How exactly does that work? so the "tune" portion is written to separate memory locations at the same time for redundancy, is that what im understanding? I just managed to get the code to compile on my machine early today cause i thought maybe there was a build target directly for this chip that i could compile but I'm a very limited in knowledge on some of this stuff and trying desperately to fill the gaps in. managed to compile it but couldnt find a way to flash the ecu with my own binary, I'm guessing i need to understand the openocd CLI right? such a learning curve I apologize in advance...

biohazardav wrote: ↑

Mon May 17, 2021 5:35 am

How exactly does that work? so the "tune" portion is written to separate memory locations at the same time for redundancy, is that what im understanding?

The biggest thing is the fact that you cannot just update 100 bytes on stm32f7 flash - you have to erase and write complete memory page and those are not your SD card 512 bytes pages, those are you to 512K pages - i.e. to update 100 bytes you have to really update all half a megabyte, and if power is turned off you corrupt all content not just your 100 bytes.

To make things more reliable yes we update two clones of tune in two of these pages. Thus we need to know position of those two for all chips we support. Because of chip shortage drama we had no choice but to fabricate 0.6 with a version of stm32 we have not used previously. It comes with minor differences we have not paged proper attention at. We did not handle this 0.6 to my own satisfaction, you should not be the one reporting issues that trivial Somehow I was able to get my not default v12 tune into both of these units you and David have so I am a bit puzzled on what's the defect but seems like we have one

AndreyB wrote: ↑

Mon May 17, 2021 6:04 am

Somehow I was able to get my not default v12 tune into both of these units you and David have so I am a bit puzzled on what's the defect but seems like we have one

The first flash works - subsequent erase operations don't work. The first one looks like it worked because it was already erased, but the next erase didn't work. We were erasing the wrong page on 1MB devices. Part way fixed, will PR tomorrow (Monday) probably.

that explains a lot because all of the suggested firmware does succeed in uploading and operation but the moment tuner studio connects and attempts a page burn the unit begins to complain.

We have a change! Please try https://rusefi.com/build_server/rusefi_bundle_proteus_f7.zip

Yes, finally sussed out all the problems with the 1MB F7, should work perfect now!

That did it! Ill go ahead and print a case and get rockin with this thing.

biohazardav wrote: ↑

Wed May 19, 2021 4:41 am

That did it! Ill go ahead and print a case and get rockin with this thing.

Excellent!