Code Monkey home page Code Monkey logo

vesc_bms_fw's People

Contributors

dnordahl83 avatar johanradinn avatar kasperradinn avatar vedderb avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

jfriesen222 variesc luna-cycle webst radinnab lebill369 zzfd97 rjmcdougall powerpan1990 bgkyer lijian8 mark2021mhd xiaoshzx yxz406 cxzhou-shadow zoupf1991 anson2001 pkstudiogithub vengo81 thuttu lzh23256 306maxi artideus ruidian mahui3653 manmuqingshan charclo cnheider benzjimny abdulkadir-muhendis acidtech zyc-waceen alonlyme capeter123 tjrong linuxhan zhengfengran sk-px embedded-tech teslafly hailong123-qu dragocytus baymaxlily mfkiwl hermixy uid-serendipity 54chenjq rd2sl battery-energy-system charlesatom wangxiaohui1029 miazgus tbayraktar himavanth-yulu s070388s stmen shiauweizhao zhangkunyi zubairahmed01 smartiotmaker devttys1 hixixtech boopathy-prabhaharan xu615888 dawnzon lex168 tomblarom step305 liyafeng888888 tutu886 chenbf jkh920184196 georgebenett krishan0507 muratdevinno moshangliu luowanhua liqiangfly elak67 dcgit00

vesc_bms_fw's Issues

Is STM32L476 overkill?

The STM32L476 seems to be overkill for this application.
Is there any reason why a STM32L432 could not be used?
It is also supported by ChibiOS, and has sufficient flash for the size of compiled code.

soc estimation algorithm accuracy

Thank you for your hard work on the project. I would like to know how the soc estimation method of the project was obtained and how accurate is it

Build on MacOS

Build on MacOS fails.

user@MBP-von-user vesc_bms_fw % make
Linking build/vesc_bms.elf
/Applications/ArmGNUToolchain/13.2.Rel1/arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: /Applications/ArmGNUToolchain/13.2.Rel1/arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard/libg.a(libc_a-signalr.o): in function `_getpid_r':
signalr.c:(.text._getpid_r+0x0): warning: _getpid is not implemented and will always fail
/Applications/ArmGNUToolchain/13.2.Rel1/arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: /Applications/ArmGNUToolchain/13.2.Rel1/arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/lib/thumb/v7e-m+fp/hard/libg.a(libc_a-signalr.o): in function `_kill_r':
signalr.c:(.text._kill_r+0x12): warning: _kill is not implemented and will always fail
lto-wrapper: warning: Options to '-Xassembler' do not match: -alms=build/lst/crt1.lst, -alms=build/lst/hal.lst, dropping all '-Xassembler' and '-Wa' options.
lto-wrapper: warning: using serial compilation of 2 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information
/Applications/ArmGNUToolchain/13.2.Rel1/arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: /Applications/ArmGNUToolchain/13.2.Rel1/arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/thumb/v7e-m+fp/hard/libgcc.a(unwind-arm.o): in function `get_eit_entry':
unwind-arm.c:(.text.get_eit_entry+0x90): undefined reference to `__exidx_start'
/Applications/ArmGNUToolchain/13.2.Rel1/arm-none-eabi/bin/../lib/gcc/arm-none-eabi/13.2.1/../../../../arm-none-eabi/bin/ld: unwind-arm.c:(.text.get_eit_entry+0x94): undefined reference to `__exidx_end'
collect2: error: ld returned 1 exit status
make: *** [build/vesc_bms.elf] Error 1

UART support Timeline

Any chance we can get basic UART support? Maybe just periodic status messages so can log that data?
Thanks

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.