neosd
Neosd Developer
- Joined
- Oct 18, 2016
- Posts
- 956
GadgetUK,
Dont get me wrong, but we cant keep wasting more time with the issues you may have on this firmware, cause we know its broken. It was a test firmware. We changed more things than timming on this firmware, i wont explain what we changed, but those changes were really deep. It was intended as a test, it didnt woked so we have decided to not follow this road anymore.
We would like to focus on issues with retail firmware.
We think that we know whats happening to Nostromo and its not a timming issue. We may be wrong cause it would not be the first time we are wrong, but we have to focus, telling people that there is a timming issue only sends a wrong message.
I hope you understand my point, lets move on, and focus in whats important, you got a replacement neosd comming that will arrive in 3 or 4 days, once you get it, we will continue giving you support to know what happened there, but until this day, focusing things on your nesod and your firmware is a totally waste of time and may only end confussing others.
Thanks
Dont get me wrong, but we cant keep wasting more time with the issues you may have on this firmware, cause we know its broken. It was a test firmware. We changed more things than timming on this firmware, i wont explain what we changed, but those changes were really deep. It was intended as a test, it didnt woked so we have decided to not follow this road anymore.
We would like to focus on issues with retail firmware.
We think that we know whats happening to Nostromo and its not a timming issue. We may be wrong cause it would not be the first time we are wrong, but we have to focus, telling people that there is a timming issue only sends a wrong message.
I hope you understand my point, lets move on, and focus in whats important, you got a replacement neosd comming that will arrive in 3 or 4 days, once you get it, we will continue giving you support to know what happened there, but until this day, focusing things on your nesod and your firmware is a totally waste of time and may only end confussing others.
Thanks
You know what, I am not mixing things at all (he's on a different firmware to me with the same problem), and to be honest I am starting to feel patronised by some of the replies I keep getting recently. Like I am on a beta firmware so that explains all the problems.
The glitch that was reported today - the fact it is intermittant can only be timing related, and you know what - every problem I've had so far (and the few that others have had) are all timing related from what I can see. Intermittancy in CRC checks, line glitches, and now that issue in Pulstar, they would lead anyone to think there's a timing issue somewhere that has the behaviour of either cross talk or something that is not correctly locked via PLL.
I am being patient, and I will continue to do more tests when the other cart arrives next week, and you might not think what I suggest is helping but it's just my opinion at this point in time. That doesn't mean I am saying that the issues I am experiencing cannot be solved, I am not trying to create problems here at all, I am just starting to lose my patience tbh.