canopen-stm32f7xx

KO | EN

gitlite — search

#hacktoberfest #ai #android #rust #deep-learning #docker #nodejs #java #windows #awesome #cli #kubernetes #vue #openai

canopen-stm32f7xx

(★ 10)

CANopen quickstart application for the STM32F769 to illustrate how the free CANopen Stack is used in your project.

canopen-stm32f7xx 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Repository Structure

```
+- cmake        : submodule referencing the repository 'cmake-scripts'
+- debug        : debugger configurations
+- dependencies : external managed components
+- src          : canopen example project
|  +- app       : application source code
|  +- config    : configuration of startup and HAL
|  +- driver    : canopen target specific drivers
```

# CANopen Demo for STM32F7xx Microcontrollers

This project demonstrates the usage of the free [CANopen Stack Project](https://canopen-stack.org). The included application is the Quickstart - "*CANopen clock application*", described in detail at the [project website](https://canopen-stack.org/latest/start/quickstart/).

We use the [STM32Cube MCU Full Package for the STM32F7 series](https://github.com/STMicroelectronics/STM32CubeF7) made by ST Microelectronics as the low-level foundation for the chip configuration, the startup, and the driver implementation. With some slight enhancements to match our CMake build environment, we provide a small source code package out of a [forked repository](https://github.com/embedded-office/STM32CubeF7) for integration in our demo projects.

My hardware setup for this development and testing is:
- the [32F769IDISCOVERY Discovery kit](https://www.st.com/en/evaluation-tools/32f769idiscovery.html)
- a CAN tranceiver [Waveshare SN65HVD230 CAN Board](https://www.waveshare.com/sn65hvd230-can-board.htm)
- an Atmel [AT24C256 I2C EEPROM](https://www.microchip.com/en-us/product/AT24C256C)
- the [KVaser USBcan II HS/HS](https://www.kvaser.com/product/kvaser-usbcan-ii-hshs/) for CAN bus monitoring
- the [Saleae Logic Analyzer](https://www.saleae.com/) for low level measurements

The wiring is pretty simple. For your reference, see the essence in a small diagram:

![Collection of relevant hardware information](https://raw.githubusercontent.com/embedded-office/canopen-stm32f7xx/main/doc/image/discovery-can-connection.jpg)

For details, check:
- the [User Manual for Discovery kit with STM32F769NI MCU](https://www.st.com/resource/en/user_manual/um2033-discovery-kit-with-stm32f769ni-mcu-stmicroelectronics.pdf)
- the [STM32F769xx Datasheet](https://www.st.com/resource/en/datasheet/stm32f769ni.pdf)
- the [Reference Manual for STM32F76xxx MCUs](https://www.st.com/resource/en/reference_manual/dm00224583-stm32f76xxx-and-stm32f77xxx-advanced-arm-based-32-bit-mcus-stmicroelectronics.pdf)

## Usage

### Development Tools

Download and install these free tools for your system:

- Install the build tools [Cmake](https://cmake.org/)
- Install the build system [Ninja](https://ninja-build.org/)
- Install the cross-compiler [Arm GNU Toolchain](https://developer.arm.com/Tools%20and%20Software/GNU%20Toolchain)
- Install the [STM32CubeProgrammer](https://www.st.com/en/development-tools/stm32cubeprog.html) for uploading the program to the microcontroller.

> *Note: during development, you can alternatively use the free evaluation [Ozone debugger](https://www.segger.com/downloads/jlink/) with the [ST-Link Reflash Utility](https://www.segger.com/products/debug-probes/j-link/models/other-j-links/st-link-on-board/) from Segger.*

### Submodule: cmake-scripts

The basic collection of re-usable CMake scripts are placed as a Git submodule in the directory `/cmake`. The Git submodule is a reference to a specific commit hash of the Git repository [cmake-scripts](https://github.com/embedded-office/cmake-scripts).

*Small reminder: when cloning this repository you need to initialize and update the submodules:*

```bash
# clone Git repository and initialize submodules:
$ git clone --recurse-submodules <repository>

# or, in case you have already cloned the Git repository:
$ git clone <repository>
$ cd <repository-directory>
$ git submodule update --init
```

### Project dependencies

We use two extern managed components to build our target application. When using external projects it is important to define naming rules for exported CMake `target` names to eliminate name collisions.

For the example application in this repository we use:

- Target [stm32f7xx-hal](https://github.com/embedded-office/STM32CubeF7) - a fork of the STM32CubeF7 package with enhancements for usage with CMake
- Target [canopen-stack](https://github.com/embedded-office/canopen-stack) - the free CANopen Stack, provided by Embedded Office

*Note: The used versions of the dependencies are defined in the directory `/dependencies`.*

## Build instructions

Just type in the project root directory:

```bash
# configure the project for debugging
$ cmake --preset debug

# build the application for your target
$ cmake --build ./build/debug
```

The target image file `canopen-stm32f7xx.elf` and the corresponding map file `canopen-stm32f7xx.map` are generated and placed in `out/debug`.

## Load and Executing on target

For the Ozone debugger there is a basic debugger configuration `debug/ozone.jdebug`, which loads the image to the target and runs to function `main()`.

- power up your STM32F769 discovery board
- double-click the debugger configuration
- watch the uploading and running to main ...

... and have fun playing with this tiny CANopen quickstart application :)

If you encounter any improvement in descriptions, project setup, build system, implementation or documentation, please rise an issue and help me to simplify the life of Embedded software engineers.

canopen-stm32f7xx

canopen-stm32f7xx 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

canopen-stm32f7xx

canopen-stm32f7xx 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README