New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proteus f7 firmware compile fails, vw_b6.lua, 8000 bytes from string of 1073 #5413
Comments
did you run |
I just attempted after your reply this was the output of gen_config_board.sh: `cyrax@DESKTOP-JKUDFGM /cygdrive/c/rusefi/rusefi/firmware BUILD SUCCESSFUL in 6s |
Over the phone I was attempting to ask to open https://github.com/rusefi/rusefi/issues and search for "lazy" |
Duplicate of #5225 which has manual instructions |
Technically real question is "why would anyone need to compile while not contributing improvement or reporting issues"? @biohazardav ? |
I don't normally run into many issues compiling and my contributions are little because my only modification is to the init_tps.cpp because the code does not play nice with the accelerator pedals i often use. I can't contribute to code because i am not a experienced coder. I dont think my input would be as helpful as others. I understand your frustration, and i will not call you again. I understand this stuff can consume more time especially when people dont go through the proper channels for help or information and I am trying to do what i can do for the 4 or so current boards im running before asking for help. |
@biohazardav please help by documenting why do you need a custom init_tps.cpp not on this ticket |
During compilation of Proteus f7 firmware, compiler stops, log output shows vw_b6.lua warning "strncpy truncated copying 8000 bytes from a string of length 10731 [-Wstringgop-truncation]
Hardware
To Reproduce
Steps to reproduce the behavior:
download master, attempt to compile with proteus selected as board and CPU set to ARCH_STM32F7
Expected behavior
successful compilation of F7 proteus bin.
Additional context
I attempted a couple workarounds such as not treating warnings as errors being disabled, which successfully compiled and board appeared to function but was unsuccessful at communication with console or tunerstudio. Appears the problem affects the pages sent from the board and the generated ini does not fix this.
The text was updated successfully, but these errors were encountered: