Search

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 29 Mar 2006 09:55 AM by  vmo
Starting Lolo just outputs garbage.
 22 Replies
Sort:
You are not authorized to post a reply.
Page 1 of 212 > >>
Author Messages
Andy Daytona
New Member
New Member
Posts:4


--
10 Jul 2005 10:56 AM
    Hi,

    I have the 5475EVB rev B and I am trying to start lolo from dBug.
    I start it with the command go ff840000

    Two LEDs on the board starts blinking alternately and I get garbage text
    in my terminal.

    It seems to understand what I am typing because different command give different amounts of garbage...

    I tried upgrading to the latest version on the Logic website but nothing changed so I suppose it was the latest version from the start.

    My terminal is set to 115200bps.
    dBug works fine at 115200...

    Does anyone have a clue to what is happening?
    Anonymous
    Posts:


    --
    11 Jul 2005 11:00 AM
    Hello Andy,

    Have you tried reseting the terminal? This can be done by going to Control > Resest Terminal. This might fix things, please post back here if it does not.

    Thank you,
    Andy Daytona
    New Member
    New Member
    Posts:4


    --
    11 Jul 2005 11:14 AM
    Hi,

    yes, I tried resetting the terminal and now I tried it again just to be sure.
    It doesn't help unfortunately...

    Characters are echoed back correctly when I type them, not for example backspace, though instead I see a B and then next time a space+circle and then a B again.
    Anonymous
    Posts:


    --
    11 Jul 2005 11:23 AM
    Hello Andy,

    It almost sounds like you have the wrong version of LogicLoader. It is possible that when you registered your kit you may have selected the wrong one. Can you email me directly so I can ask you a few questions offline to get this solved?
    Andy Daytona
    New Member
    New Member
    Posts:4


    --
    11 Jul 2005 12:08 PM
    Certainly, silly question; how do I obtain your e-mail?
    Or if you have my e-mail, e-mail me instead.
    Andy Daytona
    New Member
    New Member
    Posts:4


    --
    13 Jul 2005 07:11 AM
    I have found that for some reason the Logic Loader configures PSC0
    wrongly on my board.

    PSCMR10 (0x10008600) contains 0x01 (6bit, parity) instead of 0x07 (8 bits, no parity)

    If I change this using a BDM debugger and then continue execution everything works.
    MH
    New Member
    New Member
    Posts:


    --
    09 Mar 2006 07:57 AM
    I received the M5474LITEKIT yesterday and appear to have the exact same problem described in the original post. All I have done so far is follow the instructions in the QuickStart Guide (to the letter and several times) and yet LogicLoader does not work.

    I see that some people have been using LogicLoader and some have been having problems. I'd like to know how those that had a problem fixed it? I don't want to have to use the BDM debugger every time I want to use LogicLoader. And why is a problem that was described over six months ago still there? The label on my board says it is rev 3.
    Anonymous
    Posts:


    --
    09 Mar 2006 03:32 PM
    MH,

    Can you get me some information?

    What's the part number on your FireEngine? You can find this information at the following link:

    https://www.logicpd.com/auth/serial_no.php

    Have you gotten LogicLoader to work with the change described in this thread? If so what version of LogicLoader are you using?

    Are you certain that you're setting the baud rates correctly for LogicLoader?

    Thanks,
    MH
    New Member
    New Member
    Posts:


    --
    10 Mar 2006 01:51 AM
    Aaron,

    The part number is 1001308 (Rev 3).

    I have not tried using the BDM debugger as described in this thread as it sounded like something that would have to be done everytime I needed to use LogicLoader. The output certainly behaves as if the communications settings are wrong but I have not been able to find a setting on HyperTerminal that allows proper communication (Tera Term is limited to only 7 or 8 bits).

    I compared the memory at FF840000 with the five versions of lolo that you have on your website and it appears to be version 1.5.4. That is the only one that has 600006B6 at FF840000-FF840003 which is the same as my unit.

    I am absolutely certain that I have set the baud rate correctly and I have also tried other settings without success.

    Regards,
    Malcolm
    Anonymous
    Posts:


    --
    10 Mar 2006 12:02 PM
    Hi Malcom,

    If you're using LogicLoader 1.5.4 please update to the latest version which is 2.0.5.

    http://www.logicpd.com/do...ves/1518/1004072.zip

    You can reference this doc for how to do this the CF flasher.

    http://www.logicpd.com/do...56/1000199_Rev_C.pdf

    Once this is done please let me know if you're still having these same issues.

    Thanks!
    MH
    New Member
    New Member
    Posts:


    --
    13 Mar 2006 05:24 AM
    Aaron,

    I loaded the latest version of LogicLoader using the 1004072_dbug_lolo srec file which set the baud rate back to 19200. I then changed the DBUG baud rate to 115200 and checked that DBUG appeared to be working ok. When I entered GO FF840000 I received the same garbage as I did before I updated the flash. I am using Tera Term set to 115200, 8 bits, no parity, 1 stop bit, no flow control, no delays. It appears to be using a different serial configuration although using HyperTerminal (since Tera Term has limited settings) I haven't been able to find a configuration that will work.

    If I can't get LoLo to work I'll just stick with DBUG and CFFlasher since they appear to be reliable.

    Regards,
    Malcolm
    Anonymous
    Posts:


    --
    13 Mar 2006 04:08 PM
    Malcom,

    I am sorry you having trouble with LogicLoader. I have not been able to reproduce the problem you are seeing. You may want to try re-seating the board on you development kit. If you don't mind trying, you could also use the flasher to overwrite DBUG with the appropriate version of Logicloader at 0xff800000. You can always use the flasher to go back to DBUG if you like.

    Good luck,
    Bruce
    Anonymous
    Posts:


    --
    15 Mar 2006 03:13 PM
    Malcom and Andy,

    I have figured out the problem. LoLo has a bug where instead of enabling RTS to send by writing to the psc->opset register, it is writing to the psc->mr register by mistake. Since we have already written to the psc->mr register once, it has advanced the bank pointer to mr2. The erroneous write clobbers the 7 we had just written into mr2. The net effect of our erroneous write is to change the width of the stop bit to .625 instead of the 1 we were aiming for. Evidently for most users, having RTS enabled and a full width stop bit are not required for proper operation. This explains why we have rarely seen the problem reported.

    Andy thought he was correcting the setting in mr1 to no parity, 8 bits. Fortunately for him he erroneously deduced that 7 was the correct setting for mr1 when in fact it is amazingly enough, the correct setting for mr2 as noted above. The correct setting for mr1 is 0x13 to select no parity, 8 bits. When you read mr1, which is possible by writing a 0x10 to the command register, you see 0x33 but that is because bit 5 is stuck at 1 which is explained in the manual. Thus contrary to Andy's post, we are in fact setting the psc for no parity with 8 data bits.

    This bug will be fixed in the next release of LogicLoader.

    Bruce
    MH
    New Member
    New Member
    Posts:


    --
    16 Mar 2006 01:59 AM
    Bruce,

    Thank you for the description of the bug. Do you know when the next version is likely to be available?

    Regards,
    Malcolm
    vmo
    New Member
    New Member
    Posts:


    --
    16 Mar 2006 10:52 AM
    I have the same problem, however, I would like to present something that I think is very interesting. I have two m5474 Zoom lite eval boards and I've been trying to work with them on 4 different machines. LogicLoader v. 2.0.5-MCF5474_10 0001 are installed on both of the boards. On two of the computers, both of which have onboard serial ports, the target and the host are able to communicate with each other fine. However, on the hosts that are using pci parallel/serial combo cards, the problem described in this discussion arises. The output from the board appears as garbage, but the board is able to echo the inputs back. When the data bit is set to 7, the output is displayed correctly on the terminal but the target doesn't echo any input sent to it.

    So what versions of LOLO does this bug reside in?
    MH
    New Member
    New Member
    Posts:


    --
    17 Mar 2006 01:58 AM
    Thank you for that observation. The serial port on the computer I am using is on a pci card rather than on the mother board so fits your experience. I haven't tried it on any other computer but will try it later using a laptop. That may allow me to use LoLo before the bug is fixed.
    Anonymous
    Posts:


    --
    17 Mar 2006 08:54 AM
    Hello,

    The bug is in all versions of LogicLoader prior to the upcoming version 2.0.6. We are hoping to release version 2.0.6 on the Coldfire by March 24, 2006.

    Perhaps the problem that vmo is seeing is related to RTS not being asserted properly due to the current bug.

    Thanks,
    Bruce
    Anonymous
    Posts:


    --
    22 Mar 2006 04:14 PM
    Hello,

    If you are interested in testing a pre-release version of 2.0.6 to verify that it fixes the problem that you are seeing with the serial port please email platformsupport@logicpd.com and we will send it to you and would be happy to get your feedback.

    Thanks,
    Bruce
    MH
    New Member
    New Member
    Posts:


    --
    27 Mar 2006 02:04 AM
    Bruce,

    I've just tested the pre-release version of LoLo (2.0.6) that starts at FF840000 and the serial communication problem is now fixed. Thank you.

    Regards,
    Malcolm
    vmo
    New Member
    New Member
    Posts:


    --
    28 Mar 2006 03:33 PM
    I have the prelease version of the 2.0.6 lolo on my 5474 board. I just discovered that when I try to load an elf file from either tftp or serial (thru tera term) lolo hangs after the file's been transfered. Has this been diagnosed by anyone yet?
    You are not authorized to post a reply.
    Page 1 of 212 > >>