Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 27 Jul 2005 05:08 PM by  Anonymous
Rowley CrossWorks generated .ELF a no go with LoLo
 1 Replies
You are not authorized to post a reply.
Author Messages
New Member
New Member

27 Jul 2005 03:58 PM
    I've created a .elf file of the echo sample using the Cygwin tools. I am able to upload that .elf file in my LH75401 development board and it works as expected.

    Now, I plan on using Rowley CrossWorks for my development, so I figured I could just compile the echo project, create a .elf and then use LoLo to upload that to my development board. Well, I am able to create a .elf, but when I try to upload it using Tera Term, Tera Term goes batty and I'm forced to restart the app. Once I do, I can check the area of RAM (0x48040000) where I supposedly had loaded the .elf, but I don't see the new .elf up there.

    So, I guess my question is if anybody has used Rowley CrossWorks to generate a .elf file and then subsequently used LoLo to upload it?

    Can anyone think of potential pitfalls that I could be falling into?



    27 Jul 2005 05:08 PM
    Hi Jim,

    I haven't used Crossworks for development but I thought I'd at least point you to this FAQ to see if it helps at all, this is for ARM and Greenhills but Crossworks might be doing the same thing:

    You are not authorized to post a reply.