I suppose the ultimate question that I am asking is--- (in addition to
the ones above)-- what is the easiest way to set up the board to run my application on power-on/reset? Thanks!!

Dave Warden

Quote:
(1) How can I make LoLo boot-up at reset (instead of dBUG)?

The way I would do this would be to replace dBUG with bolo/lolo as per the instructions in this doc http://www.logicpd.com/su...viewtopic.php?t=443.

Quote:
(2) Does dBUG need to use a serial EEPROM to function properly

Yes it does. In order to use the CPLD code on your development kit you're going to need to download and sign the CPLD License agreement and send it in to sales. Specific instructions are provided in the SLA for where to send it, linked below:

http://www.logicpd.com/do...05/1000730_Rev_A.pdf

Once you have this you'll be able to program the serial eeprom.

Quote:

(3) I would like to load a file that executes from RAM in low memory--what is the easiest way to have this application execute on reset? If I link it for low memory, it clobbers LoLo; if I link it for flash memory, it wants to run from flash memory...

Once LoLo boots by default you can program the serial_eeprom with a script that will auto load your application.

Hi Aaron,

Could you check/re-post the link for the instructions to substitute BoLo/LoLo for the dBUG program? That link above references this thread. Thanks for the license agreement for the CPLD code, I'll get it back to sales ASAP.

Regards,

Dave Warden

Dave,

oops... my mistake, here's the correct link:

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

You'll want to follow the instructions in section 2.1. When you are selecting an SREC file to send you'll want to send the one that has a name similar to this

blolo_1.5.4_MCF5475_10_ITX_0001

The "blolo" indicates that this file contains both BoLo ( a stripped down version of LoLo that resides at block 0 in flash ) and LoLo. Please post back with further questions.

Thank you,

Hi Aaron,

I downloaded the srec bolo/lolo file for version 1.5.1 (1.5.4 wouldn't load because my no flash at F800:0000 problem--another problem) and burned the flash. On re-boot, the board hangs. Yet every 4th or 5th reset, Bolo comes up. Lolo never comes up unless I jump to FFE4:0000 manually from the BoLo prompt.

I don't think the board is bad because dBUG used to come up reliably after every reset. My guess is there is some flakey memory timing or some other initialization problem (remember I have no CPLD code).

SIGH! I'm not sure what to try next. Thanks for the continued help!

Dave Warden

Hi Dave,

Can you please provide a part number and revision of the Fire Engine, the actual module that is on the baseboard? You can find this by taking the SOM off the baseboard and looking at the sticker on the underside.

I think that you have an older pre-release kit that has issues that were resolved on production released boards. Freescale and Metrowerks are RMA'ing development kits to swap out older boards with new ones.

I'd suggest you pursue RMA'ing your board with whoever you got it from. In the future it's going to be more advantageous for you to have a development kit that is a current production revision and not a pre-release.

I would suggest contacting Freescale at the following link and request a rev A00 or later model through their RMA process.

https://www.freescale.com/webapp/ruhp.login.framework

Thanks,