> Hello all, > > What toolflow did you use to compile your .bof file? Someone correct > me if I'm wrong, but the only version of the CASPER toolflow that will > work with the BEE2 is 7.1. I've tried running designed built using > 10.1 on a BEE2, and this is exactly what happened. Though this was > also a long time ago.
It is my understanding that 10.1 is supposed to work with bee and ibob designs. I hope that is the case... John > > Laura > > > On Thu, Dec 17, 2009 at 7:28 AM, G Jones <[email protected]> wrote: >> Hello, >> When I've had odd behavior like this before it turned out to be a >> corrupt >> bof file. I would try recopying the design to the BEE2, but admittedly >> it's >> a bit of a long shot. >> Glenn >> >> On Wed, Dec 16, 2009 at 11:49 PM, Oussama Sekkat <[email protected]> >> wrote: >>> >>> Hi All, >>> I just compiled one of my design and ran it on Bee2. >>> I notice 2 things: >>> 1. When I run the bof file, I don't get the usual Bee2 message: >>> **************************** >>> * TinySH lightweight shell * >>> **************************** >>> Design name : bee_erg_det_v4p3 >>> Compiled on : 29-Nov-2009 23:46:31 >>> DON'T PANIC ;-) >>> Type 'help' for help >>> Type '?' for a list of available commands >>> >>> BEE2 % >>> 2. when I try to read or write a register, it just hangs! >>> Any ideas what could have gone wrong here? >>> The funny thing is that I only added a couple blocks to one of my >>> previous >>> design that worked fine! Now I'm getting this strange issue. >>> Please let me know if you ran into a similar problem before and if you >>> know how to deal with it. >>> Any input would be greatly appreciated. >>> Thanks! >>> Oussama. >> >
