Re: [myhdl-list] *** GMX Spamverdacht *** Re: *** GMX Spamverdacht *** Hello World

[Günther S. <gue...@gm...>]

Hello,
it is working:
https://github.com/stangassinger/de0_nano_adxl345
I am getting the DEVID 0xE5
The problem was not the myhdl code.
The problem was the generated verilog code.
At the beginning of the generated code where the ports are declared
it says:
output I2C_SDAT;

And this was one and only problem !!
Because the I2C_SDAT is tristate it should not be a output port.
There fore i changed it to:
inout I2C_SDAT;

And with this change it is working  :-)   :-)

But my question now is:
How do i have to declare the I2C_SDAT port in myhdl
so that it generates to "inout" ???

I declared it with:

I2C_SDAT = TristateSignal(False)

What do i have to do the it generates this code:
inout I2C_SDAT;

I would be very glad if someone could help me?
Thank you very much.
Best regards
guenther stangassinger








Am 15.05.2015 um 10:53 schrieb Günther Stangassinger:
> Hello together,
> unfortunatelly i was not really successfull with my ADXL345 reading the
> DEVID with de0-nano
> I managed to get the same sequence in simulation as someone who was
> doing the same here:
> http://www.mikrocontroller.net/topic/350597
> At the bottom you can see sequences which are quite the same, as what i get
> when i run my code in simulation with
> python gw.py
> I have my code here now:
> https://github.com/stangassinger/de0_nano_adxl345
>
> So if someone has also a de0-nano board, it would be great if he could
> test it on his board.
>
> So i am quite pleased with the output in simulation mode.(Also the
> expected tristate signal is on the right position!)
> But when i run the converted verilog code on my de0-nano
> i only get 0x0 as the output instead of 0xE5
>
> So any hints for this, mybe very small problem are very wellcome.
>
> Until now i am very convinced of myhdl but i want to transfer it to real
> word problems.
> Thank you very much.
>


-- 
Mit freundlichen Grüßen
Günther Stangassinger