As someone that has been using the 10.1 tools for almost two years, I
can confirm that they never worked for BEE2s. It would be great if
they did, so 7.1 can finally be mothballed forever.
Laura
On Mon, Jun 21, 2010 at 7:24 PM, David MacMahon
wrote:
>
> On Jun 21, 2010, at 14:54 , melvyn wright
On Jun 21, 2010, at 14:54 , melvyn wright wrote:
would regression testing have caught this ?
Maybe. The problem was introduced around the time mlib_devel was
being ported to 10.1, so it's not clear that the BEE2 user fpga base
package has ever worked under 10.1.
Dave
well done Dave.
On Mon, Jun 21, 2010 at 8:21 AM, David MacMahon
wrote:
>
> On Jun 19, 2010, at 23:01 , David MacMahon wrote:
>
> I'll let you know if I figure anything out.
>>
>
> Through multiple combinations of working 7.1 stuff and non-working 10.1
> stuff, I eventually figured out that the p
On Jun 19, 2010, at 23:01 , David MacMahon wrote:
I'll let you know if I figure anything out.
Through multiple combinations of working 7.1 stuff and non-working
10.1 stuff, I eventually figured out that the problem is due to that
fact that 10.1 XPS_BEE2_usr_base/system.mhs uses dcm_module
I think the mkbof header might have changed somewhere along the line
for ROACH/10.1. Have you tried the old mkbof from the 7.1 flow on the
10.1 flow?
Jason
On 20 Jun 2010, at 08:01, David MacMahon wrote:
On Jun 19, 2010, at 15:56 , John Ford wrote:
Hi, John,
Did you ever get any replie
Hi Mikolaj,
I am using 7.1 to build control FPGA designs without any trouble. I
have had the same results you mention when using 10.1.
Glenn
On Mon, Jun 21, 2010 at 3:18 AM, Mikolaj Chwalisz
wrote:
> Hi David,
> Yes, my emails are relating to building a BORPH enabled Linux kernel
> for BEE2 but
Hi David,
Yes, my emails are relating to building a BORPH enabled Linux kernel
for BEE2 but it is due to problem with reading registers.
I have run into the same problems as in this thread. It is impossible
to read or write registers from user FPGA compiled with 10.1 tool
chain, and control FPGA co
On Jun 19, 2010, at 15:56 , John Ford wrote:
Hi, John,
Did you ever get any replies to your query from last December?
I did not. And I have not tried to move our stuff to 10.1.
Thanks, John. I've resorted to trying two very simple test models
(identical except for the fact that one i
> Hi, John,
> > Did you ever get any replies to your query from last December?
>
I did not. And I have not tried to move our stuff to 10.1.
>
> I just built a BEE2 design using 10.1 (and mlib_devel_10_1), but I
> can't get it to work. No TinySH, and reads/writes to /proc//hw/
> ioreg/* just han
Thanks, Dan,
I think this relates to building a BORPH enabled Linux kernel 2.6 for
BEE2 using the 10.1 toolflow. I don't think it has any bearing on
building a BEE2 user fpga design using the 10.1 tools, but if it does
then it seems to imply that BEE2 development needs to stay on the 7.1
hi dave,
the attached email chain from the bee2-users list might be relevant
to your question.
dan
---
Hi, John,
Did you ever get any replies to your query from last December?
I just built a BEE2 design using 10.1 (and mlib_devel_
Hi, John,
Did you ever get any replies to your query from last December?
I just built a BEE2 design using 10.1 (and mlib_devel_10_1), but I
can't get it to work. No TinySH, and reads/writes to /proc//hw/
ioreg/* just hang.
Do I have to go back to 7.1 for BEE2 development?
Thanks,
Dave
On
Hi. Does anyone know what the status of this is? Does borph on the bee2
work under 10.1?
John
> 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
>
>
> 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
>
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 t
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 wrote:
> Hi All,
>
> I just compiled one of my design and ran
Hi Oussama,
What commands are you using to interrogate the software registers?
- Andrew
On 12/16/09 11:49 PM, "Oussama Sekkat" 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:
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
18 matches
Mail list logo
