Mar.1 eCos related errors and causes

[again: just dev notes]
Found that using GNU 3.4 with current CYGWIN seems to work best.
Error:
/cygdrive/c/Local/GNUARM/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/bin/ld: address 0x1402a0 of forte.elf section .rodata is not within region rom
Cause:
using large older LMS eCos


Error:

collect2: ld returned 1 exit status
CMakeFiles/forte.dir/core/stringdict.cpp.o: In function `CStringDictionary::getInstance()':
C:/Users/Carolyn/dev/DistCtl/fordiacWk/lms4/src/core/stringdict.cpp:16: undefined reference to `atexit'
Cause:
wrong eCos

Feb.28 Debugger notes

[again: just dev notes]
Goal: Get at least 1 (gdb with ARM7) debugger working on laptop
Sideline: Flashing LMS


OpenOCD is what has been used. Looking for something easier to install and perhaps better

• OpenOCD
• used on lab PC ver.0.3 with patch (compiled) 
• However neither 0.3 with patch (both compiled and from lab PC) nor 0.4 (installed) work
• Possibly cygwin component not installed, but so far no clear documentation to check
• Have not found any .cfg command documentation.
• TCL in .cfg files may have changed between 0.3 and 0.4
• Segger
• Edu comes comes with debug software
• Understanding may help understand OpenOCD .cfg commands
• LOOKING AT DOCS
• http://www.segger.com/cms/j-trace-arm.html
• 1.3 J-Link / J-Trace models
• JLink.exe
• HW version info

SEGGER J-Link Commander V4.22c ('?' for help)

Compiled Jan 18 2011 11:40:21

Updating firmware:  J-Link ARM V8 compiled Dec 16 2010 20:21:29

Replacing firmware: J-Link ARM V8 compiled Dec  1 2009 11:42:48

Waiting for new firmware to boot

New firmware booted successfully

DLL version V4.22c, compiled Jan 18 2011 11:40:08

Firmware: J-Link ARM V8 compiled Dec 16 2010 20:21:29

Hardware: V8.00

S/N: 268000496

OEM: SEGGER-EDU

Feature(s): FlashBP, GDB

J-Link>

• 
  

Options to Flash LMS HW:

• SAM-BA v2.10_cdc (works Lab PC (XP) & laptop (Vista))
• OpenOCD with flash cfg (works Lab PC (XP))
• Segger J-Flash

Feb. 23 Notes before flying

Blog is back to a place to keep notes
C:\Users\Carolyn\Dropbox\LMS\LMS  has the code review cleaned up code


be sure have the right working small eCos!! 
Backed up:


Lab PC:
working off of G: = my usbstick
G:\BootBlinkyTests\BootBlinkyTests\hgforte0216_blinkyWS24
Test 1: Blinky (again)
G:\BootBlinkyTests\BootBlinkyTests\
[manual clean deletes everything in bin\lms except ecos dirs (lib & include) and leave an empty src dir.
src
ws24
openocd bat
- flash fast works
- openocd works
- cd to dir with forte.elf and forte.bin works
- arm-elf-insight forte.elf
(remember for target chose: choose Remote/TCP)
 connect to target
 monitor reset;  monitor halt
set breakpoints
WORKS


....................
Laptop:
working off of F: = my usbstick
F:\BootBlinkyTests\BootBlinkyTests\hgforte0216_blinkyWS24L

Feb.18 OpenOCD on Laptop

This is just in notes form. (Formatted later when works here or in another entry.)
2/23 Update 1:
If path is set correctly, then trunk3 version of openocd appears to work.
Need to test with JTAG installed.


Additionally reinstalled cygwin with additional development tools.

2/22
In http://forum.sparkfun.com/ many have same error and no replies:  
Command handler execution failed.   
Seems like a catch all error message. Turning on debug did help see where its failing, but it fails at the 3rd line so not much help.


So tried IRCchat channel... Yes the .cfg commands changed between 0.3 and 0.4(which had started doing, but nothing that helped so far.)
So I will try and compile the trunk3 source code and see if that works... and look at /read up on 0.4 while it compiles.



Also looking at the debug output from trunk3 on lab PC may help to see where the changes occur.

2/18
Just copying Openocd files over to laptop didn't work

Installed openOCD 4

Currently trying to get the .cfg files to work correctly.

Just using v.3 (+jtag patch)  copied into a directory does not work.
And meant openOCD 4 had to be reinstalled.

Example .cfg files are only in git.

http://www.ethernut.de/elektor/tools/win/openocdwin.html

"Warning: You must install OpenOCD first before connecting your USB JTAG adapter to the PC."

I hope that means connecting not installing the JTAG.
[reinstalled (again) with JTAG unplugged]


Hope this JTAG bug does not affect JLINK, too.
https://sourceforge.net/apps/trac/openocd/ticket/31


Differences between Trunk3 0.3+patch(built) and 0.4(installed)
Directories Trunk3 has but installed v4 doesn't:

• Trunk3 built (3.0+patch):   
• autom4te.cache; 
• contrib; 
• doc; 
• ecosflash; 
• src; 
• tcl; 
• testing; (has .cfg files  in subdirs)
• tools;

Copied into 4.0 (from Trunk3): testing; tcl

• Program files installed (4.0) but not in Trunk3:
• bin; 
• board;  (has .cfg files)
• drivers; 
• interface; (has .cfg files)
• source; 
• target; (has .cfg files)

Feb.15,16 Testing env notes

cMake via gui does not seem consistent

• The same configuration seems to work sometimes and not others.
• Need to find what pattern will set all the variables corrently.
• In the meantime can change manually to the values in the screenshot from the cMake instructions in Jan. blog entry

cMake ECOS_SYSTEM_TARGET_LIBRARY
Should it be:
just the directory lms/bin/lib
or lms/bin/lib

LMS Flashing via OpenOCD:
Pattern when get error during flash process :
Cause of error: trying to change .cfg and forte.bin locations and didn't get it right.

• When openOCD-flash.bat gets an error 
• the sectors seem to have been locked somehow 
• and must be unlocked via SAM-BA
• The jtag lost connection once - pattern that caused it is not clear
• The device is no longer recognized by windows at all... have to go into boot mode again.

Question: Is there a way in OpenOCD to unlock the sectors everytime?

Using Eclipse with Dropbox files:

If files are shared on multiple computers - slow due to syncing.

In Eclipse the filenames have an extra dropbox unknown to Windows and make has problems.

Feb.15 Boot blinky, new forte, smaller eCos

Boot blinky not working.

Most obvious (and annoying) question is: 

Why did appear to work last week 
  and does not appear to work with the same forte lms now?

• Obvious answer would seem to be wrong forte.bin downloaded. 
•  Backing up to this version did not help. 
• See OpenOCD notes @ end of previous blog entry
• having a hard-code location for forte.bin can lead to wrong .bin file

Obvious tests are 

• go back to a working version 
• Summer 2010 with forte0.3 and larger eCos
• Works - but flashed only with Sam-ba so far 
• is screen shot needed? Only in case blinky stops working with this version

• hg_LMS_SummerBkup now a hg repository 
• committed all files to preserve everything this time  
• Regression test of hg version works

Then  switch out one piece at a time

• smaller eCos for larger eCos 
• Problems in code not used by LMS forte (abandoned test for now)
• hg forte 0.4 for forte 0.3
•  larger eCos for smaller eCos in current (2/16) forte  
• too large if any FBs included
• boot blinky works with larger eCos
•  working boot blinky so try again with smaller eCos
• eCos version used by DW had files 1 day newer than smaller eCos tested with
• boot blinky works with larger eCos
• HERE
• various lms code changes 
• Does the lmsmain that only does boot blinky work everywhere?
• Incrementally add the code changes back into hg
• initially with old file structure.
• then new file structure
• blinky works in new structure 
• add in avr_cntl
• add in FBs
• (only if doesn't work in new structure) move code around with incremental testing
• renames with incremental testing

Less obvious tests are:

• Is creation of forte.bin correct? 
• since was part of setup before
• what was the forte file before? 
• generalized OpenOCD -flash bat file so 
• input directory and openocd directories are variables
• and .cfg file is in the same dir as the .bat file
• New forte code changes
• in Nov an rv and vr were exchanged, but think this change is in hg version

Feb. 15,16 OpenOCD

OpenOCD bat file details

 Created dropbox dir with openocd bat files as backup

 Goal: get openocd working on my laptop

 Status: 
   Trying to change the lab PC openocd bat files so openocd can flash from a fixed location


Questions:

• Can the arm sectors be unlocked from OpenOCD or just via SAM-BA?
• yes
• flash protect 0 0 15 off
• Can .cfg files on Lab PC be used on Laptop
• So far - no, but lab pc can be in local directory
• lab pc is openOCD 3 and Laptop openOCD 4
  

Bat files examined in detail:

openocd - FLASH.bat

.cfg files will be copied here as backup, but real files used.

Not currently used:
arm-elf-objcopy
-->Copies a binary file, possibly transforming it in the process
Option
--gap-fill               Fill gaps between sections with

Files used:
D:\AA_local\eclipseWork\forte_lms_neu\bin\lms\src\forte 

-- created by ???
D:\AA_local\eclipseWork\forte_lms_neu\bin\lms\src\forte.bin

-- created from forte file

arm-elf-size D:\AA_local\eclipseWork\forte_lms_neu\bin\lms\src\forte

To see size of data downloaded to know if too big for LMS 

openocd.exe

Options:

-v display version

-f flash

C:\openocd\trunk3\src\openocd.exe -v

C:\openocd\trunk3\src\openocd.exe -f C:\openocd\trunk3\testing\examples\SAM7S256Test\prj\SAM7S256_flash.cfg -d2

.cfg files 

Here are the real instructions to open