the rld control core

avl_ready why the state_normal_or_write_burst not include read

because dq, when in the wr the comand and data can be accend, but when read add the command but the dq should wait the read back

 

avl_ready only to indication not handshake, so when avl_ready the input command could be not valid.and there is no signal show the input is valid

the cmd0 is same as cmd1, so always cmd1, the switch is no need

what actual going on is 

1) cmd0 no + cmd1 ok

task0 first assigned to cmd1, next_cmd pre-set cmd0,

if the cmd1 is executed, the pre-set is overwritten by cmd1,

else the pre-set is effective. and the same time task0 is assigned to cmd0, next_cmd still to execute the task0

cmd0 is finished,？？？？

2)cmd0 is valid + cmd1 is valid

 

next_cmd

 

conflicts how to solve:

 

aref is level not pulse

6000815108