Hello sjr,

Thanks for your question. Below are some suggestions.

1. Try erasing your application. To do this use the 'erase' command to erase the area LoLo will occupy. verify the erase has been performed using the read command. Refer to Logic Loader user manual for read and erase command specifics. Then try to reburn lolo.

2. Verify the lolo file you have is designed for your card engine and not another type of card engine.

3. Verify the Mode3 pin isn't pulled low (changes boot area) preventing Bolo from seeing/writing to flash. Refer to Application board schematics for location of Mode3 pin.

4. Have you verified the board will recognize the FLASH appropriately?
from the losh prompt type "ls /dev"
All of the devices should be listed, including FLASH.

Example:
losh> ls /dev
S : serial_eeprom 0
S : cpld_spi_one_2 0
S : cpld_spi_one_1 0
S : cpld_spi_one_0 0
S : flash0 0
S : serial_7a400_2 0
losh>

From what I understand you have two development kits, one that works and one that doesn't. Compare the output for both commands. Is anything different?

5. You can also try updating bolo to version 1.2, available from the downloads site. We usually don't recommend this, though, unless you have a JTAG programming device incase Bolo doesn't burn successfully.

6. Verify the J6 JTAG jumpers are in the correct 'normal' position. Refer to Quickstart guide for proper position.

Best Regards,
Andrew Wawra
Logic Product Development

>> 1. Try erasing your application. To do this use the 'erase' command to >> erase the area LoLo will occupy. verify the erase has been performed >> using the read command. Refer to Logic Loader user manual for read >> and erase command specifics. Then try to reburn lolo.

The 'erase' comamnd gives the same error. Why is it looking for '/dev/flash11' though - shouldn't it be /dev/flash0 ?

>> 2. Verify the lolo file you have is designed for your card engine and >> not another type of card engine.

It's fine - checked & rechecked, and loaded OK in another card engine

>>3. Verify the Mode3 pin isn't pulled low (changes boot area) >>preventing Bolo from seeing/writing to flash. Refer to Application board >>schematics for location of Mode3 pin.

Checked on meter - sitting pretty at 3.3V

>>4. Have you verified the board will recognize the FLASH appropriately?
>> from the losh prompt type "ls /dev"
>>All of the devices should be listed, including FLASH.
>>
>>Example:
>>losh> ls /dev
>>S : serial_eeprom 0
>>S : cpld_spi_one_2 0
>>S : cpld_spi_one_1 0
>>S : cpld_spi_one_0 0
>>S : flash0 0
>>S : serial_7a400_2 0

Er, can't do this because the board doesn't have LoLo in it, and BoLo 1.1.1 doesn't have the 'ls' command. This is what I'm actually asking.... how can I get LoLo back into the card engine.

>>From what I understand you have two development kits, one that >>works and one that doesn't. Compare the output for both commands. >>Is anything different?

Can't do 'ls' comand on the problem board. See answer above.

>>5. You can also try updating bolo to version 1.2, available from the >>downloads site. We usually don't recommend this, though, unless you >>have a JTAG programming device incase Bolo doesn't burn >>successfully.

IT WORKED !!! Using the JTAG and the RAM debug images I updated BoLo to 1.2 and was able to blow LoLo back in.

What worries me though is why BoLo 1.1.1 on hardware Rev C1 just refused to work? We're going to be ordering about 400 of these things a year, and finding out information is like pulling teeth!

Can we do this under the 8 hours support with our 2nd zoom development kit?

Regards,
sjr.