Demonstrate the use from STM32CubeMX for my STM32-CAN hardware
Switch branches/tags
Nothing to show
Clone or download
Latest commit 44a6610 Jul 17, 2016
Type Name Latest commit message Commit time
Failed to load latest commit information.
STM32-Test - removed tranmit testmessage at power up, the testmessage is only se… Jul 17, 2016
.gitignore ... Feb 20, 2016
LICENSE Initial commit Dec 23, 2015 - changed Jul 17, 2016
stm32_test.ioc -Tesst mit STM32-Cube Dec 1, 2015


Demonstrate the use from STM32CubeMX for my STM32-CAN hardware

The following is implemented V0.1:

  • LED port handling (blue Led toggles everytime then a CAN message is received)
  • Intialize CAN1 for transmitting and receiving CAN-Frames at 500 kBit
  • USB communication as VCP (Virtual Com Port), green led toggles on receiving a lawicel line
  • Skeloton for the Lawicel Protocol:


  • add Lawicel commands:
    • baudrate settings (and some custom baudrate) ('s' and 'S')
    • open and close CAN channel ('O' and 'C') if the Channel is opened, then teh red led ist permanent on.
    • open channel in listen only mode ('L')
    • settings for timestamp ('Z')
  • the testmessage is send after power up, but now then the channel is closed by lawicel protocol, the transmission is stopped. Only then the channel is opened again by lawicel protocol, then the transmission is started again.
  • Remember: on receiving CAN frames only the blue led is toggeled.

V0.3 - now the received CAN frames are visible in the CAN-Hacker :

  • add Lawicel for receiving CAN frames (StdID and ExtID)
  • Bugfix Hardfault Error by pressing "transmit"-button in CAN-Hacker
  • propared the logic for transmitting CAN frames
  • removed the transmission of the testmessage at power-up. the test messages are only sent by receiving the tramsmit request from CAN-Hacker


  • CAN2
  • DIP switch
  • complete the Lawicel Protocol (receiving and sending CAN frames by the lawicel protocol)