Current Server Time: 01:57 (Central Europe)

#apertus IRC Channel Logs

2018/04/27

Timezone: UTC


02:22
rton
left the channel
03:57
ArunM1
left the channel
04:13
RexOrCine
changed nick to: RexOrCine|away
04:53
ArunM
joined the channel
04:58
ArunM
left the channel
05:01
ArunM1
joined the channel
06:36
Bertl_oO
off to bed now ... have a good one everyone!
06:36
Bertl_oO
changed nick to: Bertl_zZ
06:37
g3gg0
o.O
06:37
g3gg0
n8
07:11
g3gg0
left the channel
07:12
ymc98
joined the channel
08:08
se6astian|away
changed nick to: se6astian
08:10
se6astian
good day
08:48
RexOrCine|away
changed nick to: RexOrCine
08:53
ymc98
Bertl : I have a few questions. What must be the specifications of the packet? What is the format of the incoming data? Should the protocol be synchronous or asynchronous? How many peripherals would be connected to the lattice fpgas in a general use case? What encoding technique is best suited for our needs? What are the objectives for the first evaluation?
09:18
sebix
joined the channel
10:08
ArunM1
left the channel
10:20
rton
joined the channel
11:52
BAndiT1983|away
changed nick to: BAndiT1983
12:06
Bertl_zZ
changed nick to: Bertl
12:06
Bertl
morning folks!
12:09
Bertl
ymc98: it is part of the task to find an 'optimal' solution for the packet protocol
12:10
Bertl
but we can do a brain storming to find some clues and to figure out some limiting parameters
12:11
Bertl
for example, a typical use case is a CSO attached to the AXIOM Beta as well as a bunch of Plugins and Shields which need to be configured and controlled
12:12
Bertl
for the encoding side, most likely an 8/10 code would be a good start for the low level transfer ... some kind of checksum/error correction might be required on top of that
12:15
BAndiT1983
changed nick to: BAndiT1983|away
12:17
Bertl
regarding the first evaluation, you listed 'protocol design', MachXO2 SerDes, various communication tests between MachXO2 and Zynq as well as preliminary protocol implementation in HDL in your application
12:20
Bertl
realistically I do not expect 'the protocol' to be complete at the first evaluation but I expect to see working bidirectional communication between MachXO2 and Zynq with some instrumentation/measurements (e.g. error rate counter, bandwidth, latency) and a rough plan how the final protocol is going to work
12:27
RexOrCine
changed nick to: RexOrCine|away
12:46
ymc98
What would encompass bidirectional communication between MachXO2 and Zynq ( what communication protocol must we employ first )? For the rough plan for the protocol we must realize the worst case scenario ( a stress test of some sorts ) and design accordingly right?
12:53
ymc98
left the channel
13:18
Bertl
the lowest level will require bit and word synchronization between Zynq and MachXO (i.e. sync up the SerDes on both sides) to get a stable stream of data flowing
13:19
Bertl
and yes, I agree, we have to design for the worst case scenario, but only for the 'real time' portion of the protocol
13:38
RexOrCine|away
changed nick to: RexOrCine
14:03
nmdis1999
joined the channel
14:44
aombk2
joined the channel
14:47
aombk
left the channel
15:17
BAndiT1983|away
changed nick to: BAndiT1983
15:37
nmdis1999
left the channel
16:04
se6astian
changed nick to: se6astian|away
17:36
Bertl
off for now ... bbl
17:36
Bertl
changed nick to: Bertl_oO
18:05
sebix
left the channel
18:57
RexOrCine
OK. The first power board took 3 hours to get to a reasonable standard. So, yes, in theory I could have the other four done by monday.
19:03
se6astian|away
changed nick to: se6astian
19:13
g3gg0
joined the channel
20:34
BAndiT1983
changed nick to: BAndiT1983|away
21:18
TofuLynx
joined the channel
21:19
TofuLynx
Hello!
21:19
g3gg0
hi
21:33
Bertl_oO
RexOrCine: great!
21:49
RexOrCine
changed nick to: RexOrCine|away
22:24
se6astian
changed nick to: se6astian|away
22:54
RexOrCine|away
changed nick to: RexOrCine
00:05
TofuLynx
left the channel