Pumpkin, Inc.

Pumpkin User Forums

Getting Started with CubeSat Kit Software -- October 2007

If you have a general question or comment regarding the CubeSat kit, post it here.

Getting Started with CubeSat Kit Software -- October 2007

Postby aek » Fri Oct 19, 2007 3:31 am

This is a short overview on getting started with the CubeSat Kit's software.

1) Download and activate (and ultimately purchase) CrossWorks for MSP430 from http://www.rowley.co.uk. The current release is v1.4.

2) After you receive your CubeSat Kit, download and install the latest software for it. All CubeSat Kits now come with three software products: Salvo Pro for MSP430, CubeSat Kit software and EFFS-THIN for the CubeSat Kit. Software is located in http://www.pumpkininc.com/cubesat/private/software/.

For this posting, the current versions are:
salvo-pro-msp430-4.0.2-rc2.exe
cubesatkit-software-1.0.2-rc1.exe
cubesatkit-effs-thin-1.0.2-rc2.exe

You should always uninstall older Pumpkin software before installing new versions. If any uninstaller fails, you can always delete the PumpkinSalvo and PumpkinCubeSatKit directories and run the installers anew.

N.B. The standard install directory root is C:Pumpkin. Projects for Rowley CrossWorks for MSP430 should work when installed to any hard drive.

3) Open the CrossWorks for MSP430 solution C:PumpkinCubeSatKitExampleMSP430MSP430x1xxCubeSatKit_Dev_BoardTestTest1RA430Pro-lib est1pro-lip.hzp . This projects builds the test & validation code for the CubeSat Kit Development Boards and FM430 Flight Modules. Select Build -> Clean test1pro-lib and then Build -> Rebuild test1pro-lib.

4) If you get an error like this

code:
Linking test1pro-lib.hzx
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/ra430/isr.c(28): error: undefined symbol '_OSTimer'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/ra430/isr.c(71): error: undefined symbol '_OSSignalBinSem'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(1236): error: undefined symbol '_OSInit'
c:/pumpkin/cubesatkit/src/csk_utility.c(18): error: undefined symbol '_OSGetTicks'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(935): error: undefined symbol '_OSDelay'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(935): error: undefined symbol '_OSCtxSw'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(960): error: undefined symbol '_OSWaitBinSem'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(977): error: undefined symbol '_OSStartTask'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(983): error: undefined symbol '_OSStopTask'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(1249): error: undefined symbol '_OSCreateTask'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(1265): error: undefined symbol '_OSCreateBinSem'
c:/pumpkin/cubesatkit/example/msp430/msp430x1xx/cubesatkit_dev_board/test/test1/main.c(1274): error: undefined symbol '_OSSched'
Build failed

then you are being affected by an error in CrossWorks for MSP430 v1.4, outlined here: http://www.pumpkininc.com/ubb/Forum19/HTML/000047.html

To fix this, remove the Salvo Library (libsalvolra430it.hza) from the Project Explorer window (use the Delete key, or right-click and select Remove), close the Solution via File -> Close Solution, re-open the solution via File -> Recent Projects -> ...test1pro-lib.hzp, then add the library back by selecting the Salvo Libraries folder, right-click, Add Existing File, navigate to PumpkinSalvoLibRA430-v1 and add the library libsalvolra430it.hza. Once the library is in the project, right-click it, select Properties, select the Common configuration, and select File Type -> Library. The build will then succeed.

Note that this problem happens on some machines and not others, but it is always fixable using the procedure above.

To run the program on your CubeSat Kit Development Board, connect to your target by double-clicking on the TI MSP430 USB-Debug-Interface (MSPFET430-UIF) in the Targets window. On the bottom of the screen, "Disconnected" will change to indicate that you are connected to an MSP430F1611 or MSP430F1612. Then choose F5 (Start Debugging) and this will download code into the MSP430. Then choose F5 (Continue Execution) and the program will begin running. You will see the LED on the MSP430 daughterboard begin to blink.

5) If you have not already done so, connect a USB cable between the Dev Board and your PC. The required drivers are located at http://www.cubesatkit.com/driver/usb/win/ for Windows PCs and http://www.cubesatkit.com/driver/usb/mac/ for Macs. Install the USB drivers as per http://www.pumpkininc.com/content/doc/appnote/an-27.pdf .

6) With a USB cable connected to a host (9600,N,8,1, no handshaking), you will start to get timestamped messages from the Dev Board that indicate the uncorrected on-board temperature of the MSP430.

7) If you connect a null-modem cable (9600,N,8,1, no handshaking) between the Dev Board and a host you will get timestamped command and control information from the Dev Board as well.

8) The SD-card test program is located at C:PumpkinCubeSatKitExampleMSP430MSP430x1xxCubeSatKit_Dev_BoardSDSD1RA430Pro-Libsd1pro-lib.hzp . You will likely have to fix the Salvo library as in 4) above, and also the EFFS-THIN library, located in C:PumpkinCubeSatKitLibRA430csk_effs_thin-1.hza. To run the SD test program, again connect a USB cable from the Dev Board to your host, and insert a blank and formatted SD card into the Dev Board's SD card socket.

------------------

[This message has been edited by aek (edited October 19, 2007).]

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby aek » Fri Oct 19, 2007 3:35 am

USB output for Test1 looks like this:
code:
1:0000000097 TalkUSB: Ambient temp is 22 C
1:0000000206 TalkUSB: Ambient temp is 22 C
1:0000000314 TalkUSB: Ambient temp is 22 C
1:0000000422 TalkUSB: Ambient temp is 22 C
1:0000000530 TalkUSB: Ambient temp is 22 C
1:0000000638 TalkUSB: Ambient temp is 22 C

------------------

[This message has been edited by aek (edited October 19, 2007).]

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby aek » Fri Oct 19, 2007 3:37 am

And I/O from the DB-9 for Test1 on the Dev Board looks like this:
code:
0:0000000000
0:0000000000 DoCmds: CSK_ Test/Demo v0.3.15.
0:0000000001 TaskStatusMonitor: Starting.
0:0000000002 TaskMeasureAmbientTemp: Starting.
0:0000000003 TaskExerciseIO: Starting.
0:0000000050 DoCmds: Control via RS-232 I/F at 9600,N,8,1.
0:0000000096 TalkUSB: Acquired USB/MHX I/F for USB.
0:0000000100 DoCmds: Test code.
0:0000000110 TalkUSB: Sending to USB.
0:0000000111 TalkUSB: Released USB/MHX I/F.
0:0000000150 DoCmds: Microhard MHX modem, 9600,N,8,1.
0:0000000200 DoCmds: Starting.
0:0000000201 DoCmds: h|?: Commands: {h|?, d, i, m, r, s, t, v, x, z}
0:0000000204 TalkUSB: Acquired USB/MHX I/F for USB.
0:0000000218 TalkUSB: Sending to USB.
0:0000000219 TalkUSB: Released USB/MHX I/F.

------------------

[This message has been edited by aek (edited October 19, 2007).]

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby aek » Fri Oct 19, 2007 3:41 am

USB output from SD1 looks like this, but only when an SD card is fitted in the SD card socket:
code:
1:0000000055 Task_Blink_P1p0: Starting.
1:0000000056 Task_Access_SD: Starting.
1:0000000071 Task_Access_SD: Opened file CSK_TEMP.TXT successfully.
1:0000000266 Task_Access_SD: Opened file CSK_TEMP.TXT successfully.
1:0000000466 Task_Access_SD: Opened file CSK_TEMP.TXT successfully.
1:0000000558 Task_Compete_for_SD(): CSK_TEMP.TXT is 567086 bytes long.
1:0000000666 Task_Access_SD: Opened file CSK_TEMP.TXT successfully.
1:0000000866 Task_Access_SD: Opened file CSK_TEMP.TXT successfully.
1:0000001058 Task_Compete_for_SD(): CSK_TEMP.TXT is 567138 bytes long.
1:0000001070 Task_Access_SD: Opened file CSK_TEMP.TXT successfully.

------------------

[This message has been edited by aek (edited October 19, 2007).]

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby aek » Fri Oct 19, 2007 3:44 am

SD1 does not have RS-232 output -- instead, it uses CrossStudio's debug I/O functionality to send messages to the Debug I/O Terminal window. SD1's output looks like this:
code:
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000006075.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000006275.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000006474.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000006684.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000006873.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000007072.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000007272.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000007481.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000007681.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000007880.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000008080.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000008279.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000008489.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000008700.
Task_Access_SD: Opened file CSK_TEMP.TXT successfully. Current ticks: 0000008876.

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby barmagan » Fri Oct 24, 2008 1:54 am

Hi, I can't get the same results from rs232 with the same codes. Can this be a hardware problem?

Another question:
Development boards bottom says revB but cubesat bus is 52pins. revB schematic shows cubesatbus less then 52 pins. Why?

Regards,

Bahadir Armagan

quote:
Originally posted by aek:
And I/O from the DB-9 for Test1 on the Dev Board looks like this:.........

barmagan
 
Posts: 7
Joined: Thu Oct 23, 2008 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby aek » Fri Oct 24, 2008 2:12 am

It's likely to be a user error -- all boards are fully tested before they leave here.

Are you using a _null-modem_ cable?

The Rev C Dev Board (that you have) incorrectly says Rev B in metal on its underside. It's a Rev C, as per the silkscreen on the top.

-Andrew

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby barmagan » Mon Oct 27, 2008 1:00 am

Yes I use null-modem cable and I get some text from the RS232 but not exactly as you've said.
I have no doubts that you test units, this is my first week with CSK stuff, before me someone else was using the modules, and I wanted to make sure that units are OK before I start developping. I faced some hardware problems and couldn't find the reason.
For example one FM430 works fine with the 5V from its adapter input but when I connect clyde power module batteries are heated too much even there is no switches and power adapter connected. I couldn't see any connection from battery terminals to FM430 directly in the FM430 schematics so I thought that power module was faulty. I connected the power module to CSK development board and another FM430 but they just worked fine. I am confused. I'll try to communicate with the power module.

NOTE:
This topic is like a tutorial and quite usefull for beginners. My messages may look awkward here. Sorry for recognizing that very late. If you like please move my messages to another topic(or just delete).

Regards,

B.Armagan

barmagan
 
Posts: 7
Joined: Thu Oct 23, 2008 11:00 pm

Re: Getting Started with CubeSat Kit Software -- October 2007

Postby aek » Mon Oct 27, 2008 4:08 am

quote:
I get some text from the RS232 but not exactly as you've said.
What did you get?

------------------

-------
aek
aek
 
Posts: 1888
Joined: Sat Aug 26, 2000 11:00 pm


Return to CubeSat General

Who is online

Users browsing this forum: No registered users and 1 guest

cron