Hercules RM42Launchpad Safety Features Demo is coming on, but with an error message.

Hello Dragan,

One option is to try and connect to the device independently of the DEMO application. There are several training videos and tutorials on how to setup and use the Launchpad that give it even more value than the DEMO application. This link will take you to a page that will walk you through setting up and running your first project with the Launchpad.

http://www.ti.com/ww/en/launchpad/launchpads-hercules-launchxl-tms57004.html#project0

If the board fails to connect to CCS as well, then perhaps the Launchpad is faulty in some way. In this case, please work with your supplier to get a replacement. If that fails, please let us know and we will try to help.

Can you try to build and load the program to your launchpad from source?
On windows, the source is typically found in folder:
C:\ti\Hercules\Hercules Safety MCU Demos\4.0.0\RM42x_target_sources

If you start CCS, and then go to menu Project -> Import CSS Project
Select search directorty: C:\ti\Hercules\Hercules Safety MCU Demos\4.0.0\RM42x_target_sources
select the discovered project
-> Finish

Press F11 to debug the project
Then Press F8 to execute it

once it's running, try to launch the demo app again by running the Windows Start menu:
Texas Instruments -> Hercules -> Hercules Safety MCU Demos -> Hercules Safety MCU Demos

Good day, when the RM42 is first used comes loaded with safety demo program and it works fine, but when I try to burn an already used launchpad sends an error to download

All:

As Jan had mentioned (Thanks Jan), if for some reason the demo application on the target is corrupted, you can load and build the application using CCS since the project is included with the installation.

The project's default location is usually located at this location C:\ti\Hercules\Hercules Safety MCU Demos\RM42x_target_sources\build in your local machine.

As an alternative, there is already an out file located in these directories at C:\ti\Hercules\Hercules Safety MCU Demos\RM42x_target_sources\build\Debug\RM42x_demo_software.out that can be programmed into the device using either Uniflash or NowFlash (if the latter is included with your installation).

Once the application is programmed into the device the Demo application on the PC should be able to communicate (make sure you assert reset after programming so the app will be executed).

Good morning.

I just tried Jan's advice of building the demo, but debug (F11) results with two errors. 

gmake: *** No rule to make target `clean'.

...
error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "RM42x_demo_software.out" not
   built
gmake: *** [RM42x_demo_software.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

Whole log file is attached. 2275.DebugErrorLog.txt

Thanks

Dragan Stanic

Hi Chuck

I am trying your advice and at moment I am at the step:

"In ‘HET1’  ‘PWM 0-7’ tab:
•
Configure PWM 0 to 75% Duty Cycle, with a Period 1000000.00uS on Pin 8"

However, graphics are terribly distorted. (attached)
 I tried different screen resolution , and it did not help.

I continued further , and since previously set a default workspace somewhere else than instructed to C:\MyWorkspace, I tried to switch workspace, but could not find menu command for it anywhere???

Thanks

Dragan Stanic

It's strange to find these two errors on a windows machine....

for the compilation error, that is not related to the example, but to your CCS installation that has to build some core libraries for the first time. Check if you have enough memory to perform this activity ( on a linux machine, I have to run the IDE as Administrator' when it needs to build these libs the first time.

The error with Halcogen is a known issue, related to your windows font size. You'll have to search the internet for the exact description. the solution is to revert any font sizes in windows to the standard setting.

I found the link to the HALCoGen error:

http://e2e.ti.com/support/microcontrollers/hercules/f/312/t/184660.aspx

Hi Dragan,

Sorry you are having trouble with the tools. I think Jan has addressed the issues quite nicely in regard to the compile errors and the graphics issue with Halcogen so I won't go into those as it would only re-hash what has already been stated. (Thanks again, Jan)

With respect to the naming of the working directory, this shouldn't matter. You do not have to follow the exact naming given in the example (although it could make it easier to follow). Just note what directory was used and replace the MyWorkspace references with your workspace name when doing the example application.

Hello Chuck,

On your advice to follow:

http://www.ti.com/ww/en/launchpad/launchpads-hercules-launchxl-tms57004.html#project0

result is:

Could you advise what went wrong?

Thanks

Dragan Stanic

Hello Chuck

Result on this one is:

So thus this confirms something is wrong with the board?

Thanks

Dragan Stanic

The compile errors in your prior post seem to indicate that the include path is not setup. One of the changes between CCSv5 and CCSv6 which it seems you have installed, is the include windows were swapped. i.e., looking at the slide presentation p.17, it is indicating to add the include path to the bottom frame/window. This, I believe, is the top frame/window in CCSv6.

In regard to your most recent post with the query "So thus this confirms something is wrong with the board?", there is a large gap between your opening "Results on this one is:" and that last statement. Is there supposed to be a screen capture or something in there? I am not seeing anything. Can you revisit and post the information you are referring to as your results?

Hallo Chuck

First,

I followed instructions from for Project0 exactly as far as possible,  up to point where discrepancy in between CCS versions in manual and latest I have made it impossible. Could you edit

http://www.ti.com/ww/en/launchpad/launchpads-hercules-launchxl-tms57004.html#project0

for CCS 6.0.1 and post it?

Second, you are right .

Screenshot is missing. It is down now:

It shows result of try to flash demo using nowFlash .

Thanks

Dragan Stanic

Hi Dragan,

There is an error in your NowFlash setup. For the CPU Family, please select "CORTEX_RXX_NODAP". The RM42Lxxx, TMS570L0x32, and RM41Lxxx silicon sets require this special setting because the DAP is not connected to the internal bus and the emulator must pass through the CPU to access memory. All other Hercules devices with the Cortex R4F CPU will use the CORTEX_RXX setting you have chosen. This is the reason for the communication error you are getting from the NowFlash tool.

Dragan,

where are you stuck with Project0?

I have a CCSv6 installation. I can check where you are stuck and indicate how it works in v6.

Chuck,

I followed your instruction and no luck,

Jan

At " First delete expand the project and delete file ‘main.c’ from CCS “Project Explorer”" i understood there is no need to delete main..c.

"Drag the HalCoGen created folders to the CCS Project" does not work, but I supposed this part is automated in CCS 6.0.1. ,

so there is no:

" Following window pop out" ,

"Choose “Link to files and recreate…”"

"Check box “Create link locations relative…”"

After that I followed including Halcogen files:

After that tried compiling , and all errors you so came up.

Thanks

Dragan Stanic

The dragging and dropping is not necessary :)

1:

When starting an example, take care that you use the same workspace for HALCoGen and CCSv6.

And that you use exactly the same name for the project in HALCoGen and CCSv6

The Project0 suggests that you use as workspace:  “C:\myWorkspace”

(I always use the workspace of CCSv6 on my PC. For me that's located in: "C:\Users\Jan\workspace_v6_0" )

2.

Do all the actions in HALCoGen, Then Save Project, Then Generate Code.

At this point you have all the sources you need. HALCoGen generated them for you.

3.

Do the initial  CCSv6 work. Just the first steps to create the project, don't change the code yet.

Skip the 'delete main.c' info. 

The 'delete main.c' remark is for older versions of CCS, that always created a new project with main.c.
For Hercules, the real main file is sys_main.c in your source folder, already generated by HALCoGen.

Skip Drag and Drop Drag and Drop is not needed. If you use the same workspace and same project name, the code is already there.

Add the include folder, as you are showing in your screenprint. I don't see anything wrong.

4.

don't change any code. Just try to compile your project by pushing the 'Hammer' button.

If you get compile errors, please list them here. Only continue to change code once the HALCoGen generated framework compiles successful.

If you are completely stuck, we can always do a Google hangout and share screens.

This Texas Instruments video got me started (again some small differences with CCSv6 on main.c and small differences in the properties dialog)

Jan,

I followed your instructions, but errors again occur.

CDT Build Console

**** Clean-only build of configuration Debug for project N4HET ****

"c:\\ti\\ccsv6\\utils\\bin\\gmake" -k clean
gmake: *** No rule to make target `clean'.

**** Build Finished ****

**** Build of configuration Debug for project N4HET ****

"c:\\ti\\ccsv6\\utils\\bin\\gmake" -k all
'Building file: ../source/dabort.asm'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/dabort.pp" --obj_directory="source"  "../source/dabort.asm"
'Finished building: ../source/dabort.asm'
' '
'Building file: ../source/esm.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/esm.pp" --obj_directory="source"  "../source/esm.c"
'Finished building: ../source/esm.c'
' '
'Building file: ../source/het.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/het.pp" --obj_directory="source"  "../source/het.c"
'Finished building: ../source/het.c'
' '
'Building file: ../source/notification.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/notification.pp" --obj_directory="source"  "../source/notification.c"
'Finished building: ../source/notification.c'
' '
'Building file: ../source/pinmux.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/pinmux.pp" --obj_directory="source"  "../source/pinmux.c"
'Finished building: ../source/pinmux.c'
' '
'Building file: ../source/sys_core.asm'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_core.pp" --obj_directory="source"  "../source/sys_core.asm"
'Finished building: ../source/sys_core.asm'
' '
'Building file: ../source/sys_intvecs.asm'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_intvecs.pp" --obj_directory="source"  "../source/sys_intvecs.asm"
'Finished building: ../source/sys_intvecs.asm'
' '
'Building file: ../source/sys_main.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_main.pp" --obj_directory="source"  "../source/sys_main.c"
'Finished building: ../source/sys_main.c'
' '
'Building file: ../source/sys_mpu.asm'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_mpu.pp" --obj_directory="source"  "../source/sys_mpu.asm"
'Finished building: ../source/sys_mpu.asm'
' '
'Building file: ../source/sys_pcr.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_pcr.pp" --obj_directory="source"  "../source/sys_pcr.c"
'Finished building: ../source/sys_pcr.c'
' '
'Building file: ../source/sys_phantom.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_phantom.pp" --obj_directory="source"  "../source/sys_phantom.c"
'Finished building: ../source/sys_phantom.c'
' '
'Building file: ../source/sys_pmu.asm'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_pmu.pp" --obj_directory="source"  "../source/sys_pmu.asm"
'Finished building: ../source/sys_pmu.asm'
' '
'Building file: ../source/sys_selftest.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_selftest.pp" --obj_directory="source"  "../source/sys_selftest.c"
'Finished building: ../source/sys_selftest.c'
' '
'Building file: ../source/sys_startup.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_startup.pp" --obj_directory="source"  "../source/sys_startup.c"
'Finished building: ../source/sys_startup.c'
' '
'Building file: ../source/sys_vim.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/sys_vim.pp" --obj_directory="source"  "../source/sys_vim.c"
'Finished building: ../source/sys_vim.c'
' '
'Building file: ../source/system.c'
'Invoking: ARM Compiler'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me --include_path="c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/MyWorkspace/N4HET/include" -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed --preproc_with_compile --preproc_dependency="source/system.pp" --obj_directory="source"  "../source/system.c"
'Finished building: ../source/system.c'
' '
'Building target: N4HET.out'
'Invoking: ARM Linker'
"c:/ti/ccsv6/tools/compiler/arm_5.1.8/bin/armcl" -mv7R4 --code_state=32 --abi=eabi -me -g --display_error_number --diag_warning=225 --diag_wrap=off --enum_type=packed -z -m"N4HET.map" --heap_size=0x800 --stack_size=0x800 -i"c:/ti/ccsv6/tools/compiler/arm_5.1.8/lib" -i"c:/ti/ccsv6/tools/compiler/arm_5.1.8/include" --reread_libs --warn_sections --display_error_number --diag_wrap=off --xml_link_info="N4HET_linkInfo.xml" --rom_model -o "N4HET.out"  "./source/dabort.obj" "./source/esm.obj" "./source/het.obj" "./source/notification.obj" "./source/pinmux.obj" "./source/sys_core.obj" "./source/sys_intvecs.obj" "./source/sys_main.obj" "./source/sys_mpu.obj" "./source/sys_pcr.obj" "./source/sys_phantom.obj" "./source/sys_pmu.obj" "./source/sys_selftest.obj" "./source/sys_startup.obj" "./source/sys_vim.obj" "./source/system.obj" "../source/sys_link.cmd" -l"libc.a"
<Linking>
warning #10366-D: automatic library build: using library "c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\rtsv7R4_A_le_eabi.lib" for the first time, so it must be built.  This may take a few minutes.
      0 [main] sh 42400 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
C:/Users/dstanic/AppData/Local/Temp/make25184-1.sh: line 1: 42400 Segmentation fault      (core dumped) c:/ti/ccsv6/tools/compiler/arm_51~1.8/bin/armar -qa c:/users/dstanic/appdata/local/temp/ti0286~1/rtsv7r4_a_le_eabi.lib *.obj
gmake.exe[1]: *** [library] Error 139
>> ERROR: mklib: gmake error during rtsv7R4_A_le_eabi.lib build
warning #10207-D: automatic RTS selection:  resolving index library "libc.a" to "c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\rtsv7R4_A_le_eabi.lib", but "c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\rtsv7R4_A_le_eabi.lib" was not found

 undefined      first referenced        

  symbol            in file             
 ---------      ----------------        
 __TI_auto_init ./source/sys_startup.obj
 exit           ./source/sys_startup.obj
>> Compilation failure

error #10234-D: unresolved symbols remain
error #10010: errors encountered during linking; "N4HET.out" not built
gmake: *** [N4HET.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

and Problems:

Description    Resource    Path    Location    Type
<a href="file:/c:/ti/ccsv6/tools/compiler/dmed/HTML/10234.html">#10234-D</a>  unresolved symbols remain    N4HET             C/C++ Problem
#10010 errors encountered during linking; "N4HET.out" not built    N4HET             C/C++ Problem
unresolved symbol exit, first referenced in ./source/sys_startup.obj    N4HET             C/C++ Problem
unresolved symbol >>, first referenced in Compilation    N4HET             C/C++ Problem
#10207-D automatic RTS selection:  resolving index library "libc.a" to "c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\rtsv7R4_A_le_eabi.lib", but "c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\rtsv7R4_A_le_eabi.lib" was not found    N4HET             C/C++ Problem
unresolved symbol __TI_auto_init, first referenced in ./source/sys_startup.obj    N4HET             C/C++ Problem
#10366-D automatic library build: using library "c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\rtsv7R4_A_le_eabi.lib" for the first time, so it must be built.  This may take a few minutes.    N4HET             C/C++ Problem

Thanks

Dragan Stanic

There is really something wrong with the CCSv6 install or with your computer:

warning #10366-D: automatic library build: using library "c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\rtsv7R4_A_le_eabi.lib" for the first time, so it must be built.  This may take a few minutes.
      0 [main] sh 42400 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump
C:/Users/dstanic/AppData/Local/Temp/make25184-1.sh: line 1: 42400 Segmentation fault      (core dumped) 

This seems to be a memory protection fault on your computer?

Are you running cygwin or another linux emulator?

As match I know, no. My system is Windows7 Professional.

Dragan

Maybe Chuck can pull in CCSv6 support here?

There is a cygwin version included with CCSv6, in the "C:\ti\ccsv6\utils\cygwin" folder.

You get a segmentation error when CCSv6 calls cygwin's  "C:\ti\ccsv6\utils\cygwin\sh.exe" 

As a workaround, can you download tha attached archive, 7838.rtsv7R4_A_le_eabi.zip

extract rtsv7R4_A_le_eabi.lib

and copy it to your :c:\ti\ccsv6\tools\compiler\arm_5.1.8\lib\ directory?

OK. It works now.

Thanks Jan.

Dragan

Perfect! You should nowx also be able to run the safety demo project from CCSv6. No need to use NowFlash in that case. CCS will load the binary file to your launchpad.

Take care that you Run the project in CCS debugger before launching the Demo application on your computer.

Good luck!

I could make demo run from CCS:

but if I run Hercules Safety MCU Demo , it is still coming with:

and reseting the board does not help it.

Dragan

Hello Dragan,

First, thank you for your patience as we work through the issues. Second, many thanks to Jan for helping to get to the root of your compile problems.

With that said, the issues with compiling is that your setup seems to not be able to create the runtime support libraries on the fly like it should be able to do. For this I have asked someone from CCS to have a look at this thread and see if they can pitch in.

Second, it seems that there is a communication issue with the Launchpad. Since you were able to connect, program and execute the demo code in the CCS debugger, this tells us there is, most likely, nothing wrong with your board. At least the XDS100v2 connection is working correctly and the device is able to run the executable.

I suspect that there is a conflict with the serial communications between the board and the PC. Have you checked the device manager to see if there are any warnings in your serial or usb devices? If so, you may need to work to resolve some conflicts before you can get the Labview based demo working. I have heard of use cases in the past where customer's Windows applications were set up to block the serial comm channels and they had to work with their IT departments to get this resolved so perhaps there is something like this going on.

In the meantime, all of the demo code and pieces of the demo code are included with the kit and you can work with them to become familiar with the device. The demo code is really only a PC based GUI that sends and receives serial commands to the Launchpad to execute parts of the code. You could very easily run these parts of the code and examine them through CCS. The only drawback is not seeing the GUI.

Dragan,

For the first problem, my suspicion is cygwin is loading components from elsewhere on your computer and this leads to the crash.

If you open a DOS window, and type C:\ti\ccsv6\utils\cygwin\sh.exe  does this crash or start the cygwin shell?

Andy

It looks like working.

Dragan

Jan,

After first project0, I tried "Exercise: Using the MibADC to collect Ambient Light Sensor data percentage df"., but this one is coming with :

"
CortexR4: GEL Output:     Memory Map Setup for Flash @ Address 0x0CortexR4: GEL: Encountered a problem loading file: C:\MyWorkspace\ADC\Debug\ADC.out Could not open file
"

By the way, I received replacement board , and it made no improvement.

Dragan.

Thanks

Chuck

I could not see any problem in Device manager.

Dragan

Dragan.

In reference to your error when trying the ADC project, did the project compile? Can you check to insure that the .out file is present and in the directory is showing in the error?

In reference to the UART connection to the Launchpad, can you put a scope on the SCITx and SCIRx pins on the Launchpad to see if you can see if there is active communication on both lines?

Regarding the core dump:  this doesn't fix the problem but might help you get past it until we figure you what is going on.  The crash happens when one of the compiler's libraries is accessed for the first time and it needs to be built. If you unzip the attached file into C:\ti\ccsv6\tools\compiler\arm_5.1.8\lib it should avoid the compiler needing to build the library.  Of course, I'm not sure if this will simply move the crash to a later point.

6710.rtsv7R4_A_le_eabi.zip

Andy,

We had done this earlier in the process before you were able to join the discussion. By doing this Dragan was able to compile and execute the code in the debugger. We were primarily curious what could be causing this type of issue since it could come again if another device type is used.

Chuck,

It may be something related to previously built and than erased ADC. C:\MyWorkspace\ADC\Debug does not have an *.out file.  Now I made same program under ADC1 name, and on " Buld Debug" it is coming with error:

Description    Resource    Path    Location    Type
#20 identifier "command" is undefined    sys_main.c    /ADC1/source    line 49    C/C++ Problem

I just checked first ADC, and find it missing curly bracket at the end.

Fix it, and it builds and deploys.

In begging terminal was giving reasonable values , but now just coming with:

" Bad file descriptor in nativilavailable"

Furthermore, I was looking for more video examples for Hercules, and there are, but with TMS570 Kit, while I got RM42 Kit. My intention is to learn enough Halcogen to be able myself creating  projects with it, as for example reading an analog voltage input value and send it as digital info, and vice versa. However videos I came across are not enough for me to fully understand the process involved. Is there some other specific tutorials or literature available for that purpose? What direction you would recommend me to go? For example, which development kit has good comprehensive literature with examples for that purpose?

Thanks

Dragan Stanic

I just encountered this with CCS v6.1.0 and RM42. I do have (pieces of) cygwin on my Win7 system; neither that sh.exe nor the one in ccsv6/utils crashes on startup.

Using the precompiled library above got me past it, with no further repercussions.