nikon/CANopenNode
1
0
Fork 0
Code Activity Actions

minor corrections

Browse source
This commit is contained in:
Janez 2020-02-06 02:26:59 +01:00
parent ae48e57c33
commit 9c0b16f981
4 changed files with 10 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
CANopen.c
View file

@ -269,7 +269,7 @@ void CO_delete(void *CANptr) {
CO_CANsetConfigurationMode(CANptr);
/* If CANopen was initialized before, return. */
/* If CANopen isn't initialized, return. */
if (CO == NULL) {
return;
}

2
CANopen.h
View file

@ -313,7 +313,7 @@ CO_NMT_reset_cmd_t CO_process(CO_t *co,
bool_t CO_process_SYNC(CO_t *co,
uint32_t timeDifference_us,
uint32_t *timerNext_us);
#endif
#endif /* CO_NO_SYNC == 1 */
/**

16
README.md
View file

@ -54,8 +54,8 @@ then NMT operational state is not allowed.
Usage of the CANopenNode
------------------------
CANopenNode itself doesn't have complete working code for any microcontroller.
It is only the library with the stack It has example, which should compile
on any system with template driver (drvTemplate), which actually doesn't
It is only the library with the stack. It has example, which should compile
on any system with blank template driver, which actually doesn't
access CAN hardware. CANopenNode should be used as a git submodule included
in a project with specific hardware and specific application.
@ -64,7 +64,7 @@ Documentation, support and contributions
----------------------------------------
Code is documented in header files. Running [doxygen](http://www.doxygen.nl/)
or `make doc` in project base folder will produce complete html documentation.
Just open CANopenNode/doc/html/index.html in browser.
Just open CANopenNode/doc/html/index.html in the browser.
Report issues on https://github.com/CANopenNode/CANopenNode/issues
@ -137,8 +137,6 @@ Flowchart of a typical CANopenNode implementation
| - Can request node |
| enumeration |
-----------------------
~~~
@ -202,10 +200,10 @@ external application. There are two:
Device support
--------------
CANopenNode can be implemented on many different devices. It is
necessary to implement interface to specific hardware, so called 'driver'.
Currently driver files are part of CANopenNode, but they will be split from
it in the future.
CANopenNode can be implemented on many different devices. It is necessary
to implement interface to specific hardware. Interface to Linux socketCAN is
part of this projects, while interfaces to other controllers are separate
projects. There are interfaces to: Zephyr RTOS, PIC, Mbed-os RTOS + STM32, etc.
Most up to date information on device support can be found on
[CANopenNode/wiki](https://github.com/CANopenNode/CANopenNode/wiki).

2
example/main.c
View file

@ -104,7 +104,7 @@ int main (void){
/* CANopen process */
reset = CO_process(CO, timer1msDiff*1000, NULL);
reset = CO_process(CO, (uint32_t)timer1msDiff*1000, NULL);
/* Nonblocking application code may go here. */