cc-tool: new package
PATCH 1/1 cc-tool: new package
cc-tool provides support for Texas Instruments CC Debugger
--- package/Config.in | 1 + package/cc-tool/Config.in | 21 +++++++++++++++++++++ package/cc-tool/cc-tool.hash | 3 +++ package/cc-tool/cc-tool.mk | 13 +++++++++++++ 4 files changed, 38 insertions(+) create mode 100644 package/cc-tool/Config.in create mode 100644 package/cc-tool/cc-tool.hash create mode 100644 package/cc-tool/cc-tool.mk
package/Config.in +1 -0
@@ -316,6 +316,7 @@ endmenu source "package/avrdude/Config.in" source "package/bcache-tools/Config.in" source "package/biosdevname/Config.in" + source "package/cc-tool/Config.in" source "package/cdrkit/Config.in" source "package/cryptsetup/Config.in" source "package/cwiid/Config.in"
package/cc-tool/Config.in new file +21 -0
@@ -0,0 +1,21 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool" + depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + depends on BR2_LARGEFILE + select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM + select BR2_PACKAGE_BOOST_SIGNALS + help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, largefile, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS
package/cc-tool/cc-tool.hash new file +3 -0
@@ -0,0 +1,3 @@ +# From http://sourceforge.net/projects/cctool/files/ +sha1 f313e55f019ea5338438633f5b5e689b699343e1 cc-tool-0.26-src.tgz +md5 26960676f3e6264e612c299fbf8ec5ea cc-tool-0.26-src.tgz
package/cc-tool/cc-tool.mk new file +13 -0
@@ -0,0 +1,13 @@ +################################################################################ +# +# cc-tool +# +################################################################################ + +CC_TOOL_VERSION = 0.26 +CC_TOOL_SITE = http://downloads.sourceforge.net/project/cctool +CC_TOOL_SOURCE = cc-tool-$(CC_TOOL_VERSION)-src.tgz +CC_TOOL_LICENSE = GPLv2 +CC_TOOL_LICENSE_FILES = COPYING + +$(eval $(autotools-package))
Signature · 1 line
1.9.1
PATCH 1/1 cc-tool: new package
Dear Marcin Bis,
Thanks for this contribution! See some comment sbelow.
Quoted 3 lines · Marcin Bis
cc-tool provides support for Texas Instruments CC Debugger
Signed-off-by Marcin Bis <[email protected]>
It is not entirely clear: is it a tool you run on your target device, or on your host/development machine?
Your package is for the target, but I would intuitively expect a debugger to run on the host/development machine. How does it work?
Quoted 8 lines
package/cc-tool/Config.in new file +2
-0@@ -0,0 +1,21 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool"
package/cc-tool/Config.in line 12
Quoted 10 lines
package/cc-tool/Config.in new file +10
-0+ depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + depends on BR2_LARGEFILE + select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM + select BR2_PACKAGE_BOOST_SIGNALS
So you're selecting libusb and boost here.
Quoted 25 lines
package/cc-tool/Config.in new file +9
-0+ help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, largefile, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADSpackage/cc-tool/cc-tool.hash new file +3
-0@@ -0,0 +1,3 @@ +# From http://sourceforge.net/projects/cctool/files/ +sha1 f313e55f019ea5338438633f5b5e689b699343e1 cc-tool-0.26-src.tgz +md5 26960676f3e6264e612c299fbf8ec5ea cc-tool-0.26-src.tgzpackage/cc-tool/cc-tool.mk new file +1
-0@@ -0,0 +1,13 @@ +################################################################################
package/cc-tool/cc-tool.mk line 11
Quoted 10 lines
package/cc-tool/cc-tool.mk new file +10
-0+# +# cc-tool +# +################################################################################ + +CC_TOOL_VERSION = 0.26 +CC_TOOL_SITE = http://downloads.sourceforge.net/project/cctool +CC_TOOL_SOURCE = cc-tool-$(CC_TOOL_VERSION)-src.tgz +CC_TOOL_LICENSE = GPLv2 +CC_TOOL_LICENSE_FILES = COPYING
But you don't depend on them anywhere here. So you are not guaranteed that they will be built before cc-tool.
package/cc-tool/cc-tool.mk line 13
Quoted 2 lines
package/cc-tool/cc-tool.mk new file +2
-0+ +$(eval $(autotools-package))
Other than that, looks good. I've checked the license info, it looks good to me. The configure script doesn't provide any option for optional things, so it looks alright.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 cc-tool: new package
Hi Thomas,
Thank you for comments.
Quoted 7 lines · Thomas Petazzoni
Dear Marcin Bis,
Thanks for this contribution! See some comment sbelow.
Quoted 2 lines · Marcin Bis
cc-tool provides support for Texas Instruments CC Debugger
Quoted 7 lines
Quoted 1 line
Signed-off-by Marcin Bis <[email protected]>It is not entirely clear: is it a tool you run on your target device, or on your host/development machine?
Your package is for the target, but I would intuitively expect a debugger to run on the host/development machine. How does it work?
cc-tool is used for interacting with Texas Instrument's Debugger and Programmer for RF System-on-Chips.
http://www.ti.com/tool/cc-debugger
The device is used for programming (and debugging) firmware on various TI Low Power RF System-on-Chips (based on 8051 microcontrolers).
I am using it for re-flashing such chips from ARM-based embedded devices (running Buildroot generated os) - so I put it under "tools for target" category.
TI chips do not have sufficient resources to run Linux on them, so adding cc-tool as a host tools in Buildroot does not make sense (in my opinion) - the tool has no use on Buildroot generated images.
Quoted 51 lines
Quoted 8 lines
package/cc-tool/Config.in new file +2
-0@@ -0,0 +1,21 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool"package/cc-tool/Config.in line 12
Quoted 10 lines
package/cc-tool/Config.in new file +10
-0+ depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + depends on BR2_LARGEFILE + select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM + select BR2_PACKAGE_BOOST_SIGNALSSo you're selecting libusb and boost here.
Quoted 30 lines
package/cc-tool/Config.in new file +9
-0+ help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, largefile, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADSpackage/cc-tool/cc-tool.hash new file +3
-0@@ -0,0 +1,3 @@ +# From http://sourceforge.net/projects/cctool/files/ +sha1 f313e55f019ea5338438633f5b5e689b699343e1 cc-tool-0.26-src.tgz +md5 26960676f3e6264e612c299fbf8ec5ea cc-tool-0.26-src.tgzpackage/cc-tool/cc-tool.mk new file +6
-0@@ -0,0 +1,13 @@ +################################################################################ +# +# cc-tool +# +################################################################################ +
Quoted 8 lines
package/cc-tool/cc-tool.mk line 11
Quoted 5 lines
package/cc-tool/cc-tool.mk new file +5
-0+CC_TOOL_VERSION = 0.26 +CC_TOOL_SITE = http://downloads.sourceforge.net/project/cctool +CC_TOOL_SOURCE = cc-tool-$(CC_TOOL_VERSION)-src.tgz +CC_TOOL_LICENSE = GPLv2 +CC_TOOL_LICENSE_FILES = COPYINGBut you don't depend on them anywhere here. So you are not guaranteed that they will be built before cc-tool.
Fixing this.
Quoted 11 lines
package/cc-tool/cc-tool.mk line 13
Quoted 2 lines
package/cc-tool/cc-tool.mk new file +2
-0+ +$(eval $(autotools-package))Other than that, looks good. I've checked the license info, it looks good to me. The configure script doesn't provide any option for optional things, so it looks alright.
Thanks!
Thomas
Signature · 1 line
Marcin Bis
PATCH v2 1/1 cc-tool: new package
cc-tool provides support for Texas Instruments CC Debugger
--- package/Config.in | 1 + package/cc-tool/Config.in | 21 +++++++++++++++++++++ package/cc-tool/cc-tool.hash | 3 +++ package/cc-tool/cc-tool.mk | 14 ++++++++++++++ 4 files changed, 39 insertions(+) create mode 100644 package/cc-tool/Config.in create mode 100644 package/cc-tool/cc-tool.hash create mode 100644 package/cc-tool/cc-tool.mk
package/Config.in +1 -0
@@ -316,6 +316,7 @@ endmenu source "package/avrdude/Config.in" source "package/bcache-tools/Config.in" source "package/biosdevname/Config.in" + source "package/cc-tool/Config.in" source "package/cdrkit/Config.in" source "package/cryptsetup/Config.in" source "package/cwiid/Config.in"
package/cc-tool/Config.in new file +21 -0
@@ -0,0 +1,21 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool" + depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + depends on BR2_LARGEFILE + select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM + select BR2_PACKAGE_BOOST_SIGNALS + help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, largefile, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS
package/cc-tool/cc-tool.hash new file +3 -0
@@ -0,0 +1,3 @@ +# From http://sourceforge.net/projects/cctool/files/ +sha1 f313e55f019ea5338438633f5b5e689b699343e1 cc-tool-0.26-src.tgz +md5 26960676f3e6264e612c299fbf8ec5ea cc-tool-0.26-src.tgz
package/cc-tool/cc-tool.mk new file +14 -0
@@ -0,0 +1,14 @@ +################################################################################ +# +# cc-tool +# +################################################################################ + +CC_TOOL_VERSION = 0.26 +CC_TOOL_SITE = http://downloads.sourceforge.net/project/cctool +CC_TOOL_SOURCE = cc-tool-$(CC_TOOL_VERSION)-src.tgz +CC_TOOL_LICENSE = GPLv2 +CC_TOOL_LICENSE_FILES = COPYING +CC_TOOL_DEPENDENCIES = boost libusb + +$(eval $(autotools-package))
Signature · 1 line
1.9.1
PATCH v2 1/1 cc-tool: new package
Hi Marcin,
package/cc-tool/Config.in line 5
Quoted 11 lines · Marcin Bis
package/cc-tool/Config.in new file +5
-0@@ -0,0 +1,21 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool" + depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + depends on BR2_LARGEFILE
LFS support is now mandatory in Buildroot. Please remove.
Quoted 6 lines
package/cc-tool/Config.in new file +6
-0+ select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM
package/cc-tool/Config.in line 21
Quoted 10 lines
package/cc-tool/Config.in new file +10
-0+ select BR2_PACKAGE_BOOST_SIGNALS + help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, largefile, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_LARGEFILE || !BR2_TOOLCHAIN_HAS_THREADS
Ditto.
baruch
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -PATCH v3 1/1 cc-tool: new package
cc-tool provides support for Texas Instruments CC Debugger
--- package/Config.in | 1 + package/cc-tool/Config.in | 20 ++++++++++++++++++++ package/cc-tool/cc-tool.hash | 3 +++ package/cc-tool/cc-tool.mk | 14 ++++++++++++++ 4 files changed, 38 insertions(+) create mode 100644 package/cc-tool/Config.in create mode 100644 package/cc-tool/cc-tool.hash create mode 100644 package/cc-tool/cc-tool.mk
package/Config.in +1 -0
@@ -316,6 +316,7 @@ endmenu source "package/avrdude/Config.in" source "package/bcache-tools/Config.in" source "package/biosdevname/Config.in" + source "package/cc-tool/Config.in" source "package/cdrkit/Config.in" source "package/cryptsetup/Config.in" source "package/cwiid/Config.in"
package/cc-tool/Config.in new file +20 -0
@@ -0,0 +1,20 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool" + depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM + select BR2_PACKAGE_BOOST_SIGNALS + help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, largefile, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS
package/cc-tool/cc-tool.hash new file +3 -0
@@ -0,0 +1,3 @@ +# From http://sourceforge.net/projects/cctool/files/ +sha1 f313e55f019ea5338438633f5b5e689b699343e1 cc-tool-0.26-src.tgz +md5 26960676f3e6264e612c299fbf8ec5ea cc-tool-0.26-src.tgz
package/cc-tool/cc-tool.mk new file +14 -0
@@ -0,0 +1,14 @@ +################################################################################ +# +# cc-tool +# +################################################################################ + +CC_TOOL_VERSION = 0.26 +CC_TOOL_SITE = http://downloads.sourceforge.net/project/cctool +CC_TOOL_SOURCE = cc-tool-$(CC_TOOL_VERSION)-src.tgz +CC_TOOL_LICENSE = GPLv2 +CC_TOOL_LICENSE_FILES = COPYING +CC_TOOL_DEPENDENCIES = boost libusb + +$(eval $(autotools-package))
Signature · 1 line
1.9.1
PATCH v3 1/1 cc-tool: new package
Hi Marcin,
Quoted 4 lines · Marcin Bis
cc-tool provides support for Texas Instruments CC Debugger
Signed-off-by Marcin Bis <[email protected]>---
[snip]
package/cc-tool/Config.in line 20
Quoted 2 lines
package/cc-tool/Config.in new file +2
-0+comment "cc-tool needs a toolchain w/ C++, largefile, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS
The comment text doesn't match the list of dependencies. Please remove "largefile".
baruch
Signature · 3 lines
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -PATCH v4 1/1 cc-tool: new package
cc-tool provides support for Texas Instruments CC Debugger
--- package/Config.in | 1 + package/cc-tool/Config.in | 20 ++++++++++++++++++++ package/cc-tool/cc-tool.hash | 3 +++ package/cc-tool/cc-tool.mk | 14 ++++++++++++++ 4 files changed, 38 insertions(+) create mode 100644 package/cc-tool/Config.in create mode 100644 package/cc-tool/cc-tool.hash create mode 100644 package/cc-tool/cc-tool.mk
package/Config.in +1 -0
@@ -316,6 +316,7 @@ endmenu source "package/avrdude/Config.in" source "package/bcache-tools/Config.in" source "package/biosdevname/Config.in" + source "package/cc-tool/Config.in" source "package/cdrkit/Config.in" source "package/cryptsetup/Config.in" source "package/cwiid/Config.in"
package/cc-tool/Config.in new file +20 -0
@@ -0,0 +1,20 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool" + depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM + select BR2_PACKAGE_BOOST_SIGNALS + help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADS
package/cc-tool/cc-tool.hash new file +3 -0
@@ -0,0 +1,3 @@ +# From http://sourceforge.net/projects/cctool/files/ +sha1 f313e55f019ea5338438633f5b5e689b699343e1 cc-tool-0.26-src.tgz +md5 26960676f3e6264e612c299fbf8ec5ea cc-tool-0.26-src.tgz
package/cc-tool/cc-tool.mk new file +14 -0
@@ -0,0 +1,14 @@ +################################################################################ +# +# cc-tool +# +################################################################################ + +CC_TOOL_VERSION = 0.26 +CC_TOOL_SITE = http://downloads.sourceforge.net/project/cctool +CC_TOOL_SOURCE = cc-tool-$(CC_TOOL_VERSION)-src.tgz +CC_TOOL_LICENSE = GPLv2 +CC_TOOL_LICENSE_FILES = COPYING +CC_TOOL_DEPENDENCIES = boost libusb + +$(eval $(autotools-package))
Signature · 1 line
1.9.1
PATCH v4 1/1 cc-tool: new package
Quoted 3 lines · Marcin Bis
cc-tool provides support for Texas Instruments CC Debugger
Signed-off-by Marcin Bis <[email protected]>
Looks good, just one small but important issue: the configure script thinks it
discovers boot in /usr/local (or in /usr if the host system has it there), and adds /usr/local/lib to the library path.
I've made a modification that avoids that and I'll repost.
Regards,
Arnout
Quoted 78 lines
--- package/Config.in | 1 + package/cc-tool/Config.in | 20 ++++++++++++++++++++ package/cc-tool/cc-tool.hash | 3 +++ package/cc-tool/cc-tool.mk | 14 ++++++++++++++ 4 files changed, 38 insertions(+) create mode 100644 package/cc-tool/Config.in create mode 100644 package/cc-tool/cc-tool.hash create mode 100644 package/cc-tool/cc-tool.mkpackage/Config.in +1
-0@@ -316,6 +316,7 @@ endmenu source "package/avrdude/Config.in" source "package/bcache-tools/Config.in" source "package/biosdevname/Config.in" + source "package/cc-tool/Config.in" source "package/cdrkit/Config.in" source "package/cryptsetup/Config.in" source "package/cwiid/Config.in"package/cc-tool/Config.in new file +20
-0@@ -0,0 +1,20 @@ +config BR2_PACKAGE_CC_TOOL + bool "cc-tool" + depends on BR2_INSTALL_LIBSTDCPP + depends on BR2_TOOLCHAIN_HAS_THREADS + select BR2_PACKAGE_LIBUSB + select BR2_PACKAGE_BOOST + select BR2_PACKAGE_BOOST_PROGRAM_OPTIONS + select BR2_PACKAGE_BOOST_SYSTEM + select BR2_PACKAGE_BOOST_REGEX + select BR2_PACKAGE_BOOST_FILESYSTEM + select BR2_PACKAGE_BOOST_SIGNALS + help + cc-tool provides support for Texas Instruments CC Debugger + for Linux OS in order to program 8051-based System-On-Chip + devices: CC254x CC253x CC243x CC251x CC111x + + http://sourceforge.net/projects/cctool/ + +comment "cc-tool needs a toolchain w/ C++, threads" + depends on !BR2_INSTALL_LIBSTDCPP || !BR2_TOOLCHAIN_HAS_THREADSpackage/cc-tool/cc-tool.hash new file +3
-0@@ -0,0 +1,3 @@ +# From http://sourceforge.net/projects/cctool/files/ +sha1 f313e55f019ea5338438633f5b5e689b699343e1 cc-tool-0.26-src.tgz +md5 26960676f3e6264e612c299fbf8ec5ea cc-tool-0.26-src.tgzpackage/cc-tool/cc-tool.mk new file +14
-0@@ -0,0 +1,14 @@ +################################################################################ +# +# cc-tool +# +################################################################################ + +CC_TOOL_VERSION = 0.26 +CC_TOOL_SITE = http://downloads.sourceforge.net/project/cctool +CC_TOOL_SOURCE = cc-tool-$(CC_TOOL_VERSION)-src.tgz +CC_TOOL_LICENSE = GPLv2 +CC_TOOL_LICENSE_FILES = COPYING +CC_TOOL_DEPENDENCIES = boost libusb + +$(eval $(autotools-package))
Signature · 6 lines
Arnout Vandecappelle arnout at mind be Senior Embedded Software Architect +32-16-286500 Essensium/Mind http://www.mind.be G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
PATCH 1/1 cc-tool: new package
In reply to Marcin BisDear Marcin Bis,
Quoted 10 lines · Marcin Bis
cc-tool is used for interacting with Texas Instrument's Debugger and Programmer for RF System-on-Chips.
http://www.ti.com/tool/cc-debuggerThe device is used for programming (and debugging) firmware on various TI Low Power RF System-on-Chips (based on 8051 microcontrolers).
I am using it for re-flashing such chips from ARM-based embedded devices (running Buildroot generated os) - so I put it under "tools for target" category.
Ok.
Quoted 3 lines
TI chips do not have sufficient resources to run Linux on them, so adding cc-tool as a host tools in Buildroot does not make sense (in my opinion) - the tool has no use on Buildroot generated images.
This is not what a host tools is. A host tool runs on your PC, i.e where you do the Buildroot build. For sure your PC has sufficient resources to run cc-tool.
Thanks,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 cc-tool: new package
Hi Thoams,
Quoted 17 lines · Thomas Petazzoni
Dear Marcin Bis,
Quoted 10 lines · Marcin Bis
cc-tool is used for interacting with Texas Instrument's Debugger and Programmer for RF System-on-Chips.
http://www.ti.com/tool/cc-debuggerThe device is used for programming (and debugging) firmware on various TI Low Power RF System-on-Chips (based on 8051 microcontrolers).
I am using it for re-flashing such chips from ARM-based embedded devices (running Buildroot generated os) - so I put it under "tools for target" category.
Ok.
Quoted 7 lines
Quoted 3 lines
TI chips do not have sufficient resources to run Linux on them, so adding cc-tool as a host tools in Buildroot does not make sense (in my opinion) - the tool has no use on Buildroot generated images.
This is not what a host tools is. A host tool runs on your PC, i.e where you do the Buildroot build. For sure your PC has sufficient resources to run cc-tool.
As I understand, host-tools are intended for doing something with images generated by Buildroot e.g. flashing, generating fs images etc.
cc-tool does not fall under this category.
It is some how similar to openocd, but openocd can be used to debug bootloader/Linux kernel running on some SoC-s (so it perfectly makes sense here).
TI chips, which cc-tool talks to - are not able to run Linux at all.
Of course cc-tool can be added to Buildroot as a host tool too. I can prepare the patch if you want.
My particular need at the moment is to have it as a tool for target.
Quoted 5 lines
Thanks,
Thomas
Signature · 1 line
Marcin Bis
PATCH 1/1 cc-tool: new package
Dear Marcin Bis,
Quoted 6 lines · Marcin Bis
Quoted 3 lines
This is not what a host tools is. A host tool runs on your PC, i.e where you do the Buildroot build. For sure your PC has sufficient resources to run cc-tool.
As I understand, host-tools are intended for doing something with images generated by Buildroot e.g. flashing, generating fs images etc.
Right.
Quoted 4 lines
cc-tool does not fall under this category.
It is some how similar to openocd, but openocd can be used to debug bootloader/Linux kernel running on some SoC-s (so it perfectly makes sense here).
Indeed.
Quoted 1 line
TI chips, which cc-tool talks to - are not able to run Linux at all.
Ok, so what you mean is that those TI chips are typically not connected to the development PC directly, but are generally connected to the embedded system that runs Buildroot.
Quoted 2 lines
Of course cc-tool can be added to Buildroot as a host tool too. I can prepare the patch if you want.
Nope, if you don't use it, don't do it. I'm fine with a target package after the explanations you provided.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com