Skip to content
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

Basic support for CC430 radio module #8811

Closed
wants to merge 8 commits into from
Closed

Basic support for CC430 radio module #8811

wants to merge 8 commits into from

Conversation

baptiste-cartier
Copy link

Contribution description

This is a basic implementation for the cc430 radio module, enabling the use of this cpu radio capabilities. It comes with a configuration example file with two example configurations, one in transmit mode and one in receive mode.

The goal of this implementation is to give a fast and simple way to use the cc430 radio module for basic communications.

Issues/PRs references

Copy link
Member

@smlng smlng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a quick one, as response to your mail: see comment, this should fix the headerguard check errors in travis.

However, besides that: please review RIOT coding style conventions, see Wiki.

}
#endif

#endif /* CC430_RADIO_H */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add newline at the end

}
#endif

#endif /* CC430_RADIO_RFSETTING_H */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add newline at the end

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I totally forgot about that one.

However, could you point me what does not comply with RIOT coding style conventions? I tried to follow them as much as I could, and I don't see which one I have not followed correctly.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see wiki for coding conventions. Also see my comments to get you started

@smlng smlng added Type: new feature The issue requests / The PR implemements a new feature for RIOT Area: drivers Area: Device drivers labels Mar 21, 2018
@baptiste-cartier
Copy link
Author

baptiste-cartier commented Mar 21, 2018 via email

* Public License v2.1. See the file LICENSE in the top level directory for more
* details.
*/

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove additional empty lines, review code below

* API for the cc1101 radio module embedded on the cc430
*
* @author Baptiste Cartier
*
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add missing closing group * @}

* @ingroup cc430
* @{
*
* @file RF1A.c
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the file name doesn't match, also we mostly omit that explicit name



/**
* @ingroup cc430
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please define a group with drivers_cc430

@smlng
Copy link
Member

smlng commented Mar 26, 2018

Before you move on here: there already is a driver for the cc110x how does this differ or improve on that?

@baptiste-cartier
Copy link
Author

The CC430 is a MCU based on the MSP430 with a radio core based on the cc1101. The means to access the radio on the cc430 is different that simply using a cc110x. Using the radio module of the CC430 implies writing specific data to specific registers of the CC430, meaning the driver for the cc110x can not be used in this context. This provides a basic mean to use the radio module and can be used as a base to build a more complex and complete API.

bcartier added 2 commits March 28, 2018 14:58
additional empty lines
missing closing group
file name and mismatch
erroneous group name
@stale
Copy link

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@stale stale bot closed this Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: drivers Area: Device drivers State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants