Wednesday, May 11, 2011

May 11 Back to Dev Env / Testing

At about this time my new Netbook Disk Drive got a problem.... so started over about 5/28

Again need to document current test environment that works.

After move to CMake (see Jan.29 hg cMake set-up)

Using GNUARM 4.1.1 in C:\GNUARM4_1_1





Testing on Laptop using Lab PC to double-check.

0.  Is the LMS seen right (=right device drivers found)? OK

  • As HW bootable device (=firmware update)
    • to be flashed with forte.bin or lego system or lejos or other firmware options.
  • As eCos device 
    • ready to test 
    • ready to send/ run a 61499 application via forte


1. Flashing the LMS firmware



  • Via Samba v2.10_cdc  - OK
    • notice with v2.10 LMS shows up as a com port and under device driver Ports no longer under Universal Serial Ports
    • Step summary: unlock, don't lock. If worked at all will be seen as eCos device now
  • Via OpenOCD
    • TODO: Need .cfg files . Must edit to match installed files <-- HERE
2. Test

  • Blinky
    • observe  (HERE - NOT Blinking ??? eCos copy? -O2 vs -O0? etc.)
    • check via OpenOCD
      • To test with OpenOCD must be compiled with -O0 not -O2, but this makes the code larger
      • Compiling with -O0 to prepare for OpenOCD testing gets a link problem that it is too large (-O2 links)!!!    CHECK eCos VERSION using
  • AVR
    • via OpenOCD check for:
      • sensor inputs
      • motor status
      • button status
  • IEC61499 Applications
    • 1 LED
    • multiple LEDs
    • sensor input
    • motors on/off












May 10 Code Clean-up / Design updates

LMS code is moving up from forte with exporter ver. 3 to ver. 4
Additionally the code is being cleaned-up from c code that works to c++ code in forte.
A set-


LMS is no longer in arch/ecos directory but in its own directory with other FBs under modules:
  • src/modules/lms: FBs and device interface code
    • open: where does platform_i2c.c /.h go?
  • src/modules/lms/lms_hw: has ecos and hw interface code
  • src/modules/lms/lms_ecos : lms ecos specific
Here is a working draft UML class diagram with design / transformation to C++
The avr controller and port manager are not yet LMS_DEV class member.
If only 1 instance of a class was currently wanted, all methods were made static.












Tuesday, May 10, 2011

May 10 Code Clean-up / Design updates

LMS code is moving up from forte with exporter ver. 3 to ver. 4

Additionally the code is being cleaned-up from c code that works to c++ code in forte.





Two shells scripts were created to take of pre- and post- build (make all)  tasks:



  • setup_lms.sh 
    • allocates bin/lms and bin/lms/src
    • copies lms ecos include and lib directories in bin directory
  • finish_lms.sh 
    • creates forte.bin






LMS is no longer in arch/ecos directory but in its own directory with other FBs under modules:

  • src/modules/lms: FBs and device interface code
    • open: where does platform_i2c.c /.h go?
  • src/modules/lms/lms_hw: has ecos and hw interface code
  • src/modules/lms/lms_ecos : lms ecos specific
Here is a working draft UML class diagram with design / transformation to C++

The avr controller and port manager are not yet LMS_DEV class member.
If only 1 instance of a class was currently wanted, all methods were made static.