DiagROM V0.9 Out

Chucky · 16 April 2017, 15:50

Just released: DiagROM V0.9

http://www.diagrom.com/

The REVISION Edition as I am at the Revision demoparty.
Whats new?

A lot of internal changes.

But changed keyboardhandling in “Manual Edit” mode, hopefully keyboard works better now.

Chipmemdetect at startup does more tests to capture more biterrors.

Also added tests if CPU can do odd/eveb reads and writes. Request by Terriblefire.

Added a testpicture as GFX Test

Added test for RTC Chip, reads both types you have to know what chip is in your machine.

Added a experimental Autoconfig support for Zorro II boards and memory, Remember that you can only run this ONCE.

Audiotest now includes several notes and waveforms and also a module.

wXR · 16 April 2017, 16:17

Hi Chucky, thanks for this. Really pleased to see that you are willing to open the source of this nice tool, and I'm looking forward to that day.

Chucky · 16 April 2017, 16:29

yes it will be open soon..

Chucky · 21 April 2017, 21:50

TOTALLY OUT OF MY COMFORTZONE NOW!

https://github.com/ChuckyGang/DiagROM

Be gentle

michaelz · 21 April 2017, 22:21

Quote:

Originally Posted by Chucky

TOTALLY OUT OF MY COMFORTZONE NOW!

https://github.com/ChuckyGang/DiagROM

Be gentle

Wow, I'll check it out tomorrow when I get the opportunity. This is a great gesture.

ross · 21 April 2017, 22:31

Quote:

Originally Posted by Chucky

TOTALLY OUT OF MY COMFORTZONE NOW!

https://github.com/ChuckyGang/DiagROM

Be gentle

If you survived on German weather and beer You can survive at github

How about integration in 'early startup-menu'? (a patched bootmenu module)

Great work and thanks!
ross

Chucky · 21 April 2017, 22:33

Early boot? nahh that is a totally different thing. and. .no..

ascp · 21 April 2017, 22:58

Thanks, nice thing to do Chucky!

Chucky · 30 April 2017, 00:23

Should I do a commit everyday I have been working on it. or more less?

wXR · 30 April 2017, 01:15

@Chucky

There's a matter of style preference to it. I think a *generally* preferred style do commits with every little change, which then makes your commit history a very useful tool for tracking changes. I recommend multiple commits, but only pushing once per day.

Chucky · 30 April 2017, 01:43

Once per day it will be.. when I am "done" for that day.

Jope · 30 April 2017, 08:32

Whatever suits your workflow. I try to do a commit per finished feature or fixed bug, that way you can use more of git's features when working with your releases.

Basically you can tag a commit to be your 0.8, 0.9 and so on. Then when development moves onwards and you decided you actually want to revert stuff but don't want to throw away all your new code, you can go back to the 0.9 tag and cherry pick individual "future" commits back to your 0.9 code and just take what you need from your new stuff.

The tool sort of shapes your work flow too in this case, but you are free to use as many or few git features as you like. If you don't want to worry about that stuff, then just do a daily commit if that's how you work best.

Chucky · 30 July 2017, 11:05

Just updated the daily version. it now have a limited version that can be programmed into 27c256 proms and to be used on A1000..

ross · 31 August 2017, 15:15

Hi Chucky, how about an hex value display in Keyboardtest screen?
I've various scancode keymaps table but only with hexadecimal value

Thanks, bye,
ross

Chucky · 31 August 2017, 15:35

Well that is an idea.. will implement

16 April 2017, 15:50	#1
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	DiagROM V0.9 Out Just released: DiagROM V0.9 http://www.diagrom.com/ The REVISION Edition as I am at the Revision demoparty. Whats new? A lot of internal changes. But changed keyboardhandling in “Manual Edit” mode, hopefully keyboard works better now. Chipmemdetect at startup does more tests to capture more biterrors. Also added tests if CPU can do odd/eveb reads and writes. Request by Terriblefire. Added a testpicture as GFX Test Added test for RTC Chip, reads both types you have to know what chip is in your machine. Added a experimental Autoconfig support for Zorro II boards and memory, Remember that you can only run this ONCE. Audiotest now includes several notes and waveforms and also a module.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
DiagROM V0.8	Chucky	support.Hardware	3	27 October 2016 13:49
New "Stable" of my DiagROM	Chucky	support.Hardware	4	07 August 2016 10:28
In search for defective custom ICs to test DiagROM	Chucky	support.Hardware	2	11 May 2015 18:49

16 April 2017, 16:17	#2
wXR Registered User Join Date: Mar 2009 Location: New York Posts: 552	Hi Chucky, thanks for this. Really pleased to see that you are willing to open the source of this nice tool, and I'm looking forward to that day.

16 April 2017, 16:29	#3
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	yes it will be open soon..

21 April 2017, 21:50	#4
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	TOTALLY OUT OF MY COMFORTZONE NOW! https://github.com/ChuckyGang/DiagROM Be gentle

21 April 2017, 22:33	#7
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	Early boot? nahh that is a totally different thing. and. .no..

21 April 2017, 22:58	#8
ascp Pastafarian Join Date: Sep 2010 Location: Uppsala/Sweden Posts: 290	Thanks, nice thing to do Chucky!

30 April 2017, 00:23	#9
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	Should I do a commit everyday I have been working on it. or more less?

30 April 2017, 01:15	#10
wXR Registered User Join Date: Mar 2009 Location: New York Posts: 552	@Chucky There's a matter of style preference to it. I think a generally preferred style do commits with every little change, which then makes your commit history a very useful tool for tracking changes. I recommend multiple commits, but only pushing once per day.

30 April 2017, 01:43	#11
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	Once per day it will be.. when I am "done" for that day.

30 April 2017, 08:32	#12
Jope - Join Date: Jul 2003 Location: Helsinki / Finland Age: 43 Posts: 9,861	Whatever suits your workflow. I try to do a commit per finished feature or fixed bug, that way you can use more of git's features when working with your releases. Basically you can tag a commit to be your 0.8, 0.9 and so on. Then when development moves onwards and you decided you actually want to revert stuff but don't want to throw away all your new code, you can go back to the 0.9 tag and cherry pick individual "future" commits back to your 0.9 code and just take what you need from your new stuff. The tool sort of shapes your work flow too in this case, but you are free to use as many or few git features as you like. If you don't want to worry about that stuff, then just do a daily commit if that's how you work best.

30 July 2017, 11:05	#13
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	Just updated the daily version. it now have a limited version that can be programmed into 27c256 proms and to be used on A1000..

31 August 2017, 15:15	#14
ross Defendit numerus Join Date: Mar 2017 Location: Crossing the Rubicon Age: 53 Posts: 4,468	Hi Chucky, how about an hex value display in Keyboardtest screen? I've various scancode keymaps table but only with hexadecimal value Thanks, bye, ross

31 August 2017, 15:35	#15
Chucky Registered User Join Date: Mar 2015 Location: Karlstad / Sweden Age: 52 Posts: 1,210	Well that is an idea.. will implement

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)