|
|
Post by Espen Skog on Nov 30, 2009 2:55:05 GMT -5
Oh YEAH....it works  I skipped going to the main office today because it got too late to drive the 8 hours last night. So I will do it today instead. BUT: Now I had teh chance to flash the 1541-3 and test that new FW you gave. It worked like a charm her are the specs. What DOES work: When starting the jdos softkernal patched for DTV: If I press F1 to dir the SDcard, it does not work. It just lists the header of the card. No errors. This was also the case with the previous FW. A load "$",8 + list works fine. Pressing F3 og manually loading a D64 image + list work PERFECT. Then the MAJOR coolnes of the all: Pressing F3 on a FILE (or load "<file>",8,1) works VERY good. 176 Blocks (bluemax -- inside a D64) loaded in 6 seconds. The Progressbar on the 1541-3 display almost stared smoking Very very ....VERY cool, Jussi. At this point, I am a very happy camper. I need to test things a bit more, though. But first impression is that it all works very nice. What did you have to fix to get this working, btw ? |
|
|
|
Post by Espen Skog on Nov 30, 2009 3:01:29 GMT -5
Hi. Now it is time for me to bring that 1581 to work and heat up the soldering iron again and make a PSU for it. I guess the pinout is easy to locate. Just need to find one of those funky DIN plugs. I wonder if maybe builing a DTV board inside the 1581 might work. That would be kinda cool. The DTV board is pretty small so it might fit. I will check it out. First I need to enjoy the new DTV case. Spent quite some evenings on making it so now it is time to play and enjoy it hehe.. Espen |
|
|
|
Post by expertsetup on Nov 30, 2009 4:52:49 GMT -5
THats great that it is working with the high speed loader Espen. That is very fast for a file that size indeed.
This information may support the idea of NTSC timing issues for my units with my Hummer, I will have to see if I still have a PAL Hummer around to test it with. that would work if I view it on my PC TV card via PAL setting I guess.
If I can find it...
|
|
|
|
Post by expertsetup on Nov 30, 2009 5:06:05 GMT -5
Ha, I found it already, so I have to attach the second 1541-III-DTV flash to the new FW and then test it. Should have time tomorrow for sure, will be great if it works. I even have a second screen wired up to a header for the second unit, they are awesome with the display, I think I will add a nice little colored LED backlight for the display. Inside a 1581 would be super sweet, would that make it a DTV-D like the 128D? A standard 12/5 adapter like the ones sold with ide/sata to usb cables should do the trick. If I were you I would just try to find that tricky DIN plug and then wire the DIN to a four pin Molex connector, would allow easy connection of the 12/5 power from a PC or the adapters I mentioned. here is a link to the adapter kit I'm talking about. www.kc-kwan.com/online/pics/o_pc_usb_ide_adapter_01.jpg |
|
|
|
Post by jsaily on Nov 30, 2009 9:44:05 GMT -5
That's good news Espen! We still need to find a way to make it work on Hummers too. I'll try to compile a set of experimental firmwares with slightly different timings, hopefully we'll find a one which works in all versions!
The F1 shortcut is a bit difficult for Jan's state machine, as it needs to re-enter into the same file after each row. I'll find a solution to this in time...
|
|
|
|
Post by expertsetup on Dec 12, 2009 14:12:23 GMT -5
It turns out that I ended up converting the PAL Hummer back to NTSC and so now I dont have a PAL unit to test with.
I'm not sure what the differences in timing for the NTSC vs PAL would be. I know that the NTSC CPU runs faster and the VICII on the NTSC runs slower than PAL.
I'll be happy to test any timing variations you may like to compile.
|
|
|
|
Post by Espen Skog on Dec 15, 2009 7:24:56 GMT -5
Hi. Just wondering if there might be any new FW released which I should try out. My dtv now works nice (although, dtv does not work with all c64 games/demos of course) and I will try to use it a little more...
Now that my HW modding is done and all works...the fun is gone :-) I got it working with the latest FW for PAL (1541-dtv-3 fw) and then I smiled, and put the box into thedrawer and have not used it since..hehehehe....
The fun is in the approach, not in the final product :-)
|
|
|
|
Post by expertsetup on Dec 22, 2009 1:34:29 GMT -5
I would be delighted to also test a new FW. |
|
|
|
Post by Espen Skog on Dec 22, 2009 8:40:45 GMT -5
Now I have started to cook a new rom filesystem to flash which has jdos as a softkernal and using SlimMenu it makes things very easy to use. HOWEVER: How the heck do I flash it ? I have made a new romfilesystem (2mb large) using dtvfsedit and tested it in x64dtv. Works nice. But, when I save it from dtvfsedit without kernal/basic inside and try to flash it on the dtv it fails. The flashing does not fail, but loading it from SDIO card into the buffer fails. It halts at the same place every time just before it is finished loading the rom. It takes like 15 mins to load 2MB with flash.prg into the buffer. So I was wondering, can someone give me a short DIY on how I do this ? Also, when I do a "LOAD" in TLR's flash utility, should I load as RAW or not ? SHould I use $000000 as loading offset ? Please heeeeelp //Espen |
|
|
|
Post by nojoopa on Dec 22, 2009 11:51:23 GMT -5
Rather off topic, but here goes... Short version: The 2MB file doesn't fit into the buffer, so split the file into smaller pieces and load & flash them one by one. Use RAW and zero offset. Long version: 1. I'll assume that the OS you're using doesn't come with a handy utility for splitting files. First, grab the latest VICE 2.2 from here. Use the flash image (with kernal/basic) you are planning to flash. Enter the VICE monitor and do the following: bank rom01
bs "flash01.raw" 0 0 ffff...and repeat it for rom02/"flash02.raw", 03, 04... 09, 0a, 0b ... 0f, 10, 11, ... 1f. Now you have 31 files, 65536 bytes each. 2. Create a new flash image file for practising. Use x64dtv with this new image file (and enable writes to the image file) for the next step. 3. Load the flash utility. Load the "flash01.raw" with offset $000000 and RAW DATA=Y and program the range $010000 to $020000 (and verify it). Then load "flash02.raw" and program $020000-$030000, "flash03.raw" to $030000-$040000, ... when the last one (flash1f) is programmed (and verified), exit the flash utility and reset. 4. Test that everything works! If it looks OK, copy flash*.raw to the SD card and do step 3 on the DTV. Good luck! Easy version: Have/get/build a dtvtrans cable and do "dtvtrans sync my_flash_image.bin"  |
|
|
|
Post by jsaily on Jan 9, 2010 2:07:31 GMT -5
I would be delighted to also test a new FW. Sorry for the delay, but I've been busy doing something completely different I'll make some new firmwares for you to test in the next couple of days. Could you PM your email address to me so I can send them directly to you. It's a bugger that I don't have any NTSC DTV or Hummer to test on so you'll need to check it. Hopefully it's just a small offset like it was for the PAL-DTV. The most serious problem in getting it to work was in the acknowledgement routines as the DTV could not pull a line down like a C64... |
|
|
|
Post by Espen Skog on Jan 13, 2010 2:37:50 GMT -5
Rather off topic, but here goes... Desperate times calls for desperate measures sometimes ;-) I wish that this small detail was mentioned somewhere in time in any forum/wiki or how-to :-) Hehe...seriously man, my house is microsoft free Don't assume the worst (just joking) So I split the file into 64kb chunks now. Hopefully it will be fine now that I know about this limit in flashtool, which is find strange. Isn't there a 2mb freespace area where the flashtool theoretically could load the whole 2mb rom image to before it flashes it ?? Thankx, I also wondered if I should go for RAW or not. Now I know. Yep. I know :-) I just ordered the diodes and the connectors and will make the cable when the parts arrive. Flashing using the 32 splitfiles is just too much manual work. I began the work, but after flashing the first part, I caved in due to the thought of doing it 32 times was just too horrifically boring. :-) Espen |
|
|
|
Post by nojoopa on Jan 13, 2010 21:52:03 GMT -5
I wish that this small detail was mentioned somewhere in time in any forum/wiki or how-to :-) Had to check... it actually is mentioned in here: "Buffer starts at $020000 so the utility can flash at max 1920kByte in one run. " Hehe...seriously man, my house is microsoft free Don't assume the worst (just joking) I tend to assume the worst and try to come with a solution that works in all platforms using software that has already been mentioned to be available (or used). The solution is rarely the easiest or best, but this usually saves typing an another message Next time someone has some question like this, please mention which OS you're using. So I split the file into 64kb chunks now. Hopefully it will be fine now that I know about this limit in flashtool, which is find strange. Isn't there a 2mb freespace area where the flashtool theoretically could load the whole 2mb rom image to before it flashes it ?? The whole 2MB doesn't fit as the Flash tool itself (and the screen and...) has to reside somewhere. Two 1MB chunks would work (and dtvmkfs has this as an output option), just drop the kernal/basic page (first 64kB) of the lower 1MB image. The reason for the 64kB recommendation was simply due to the limitations of the x64dtv monitor (I'm fairly sure that it can't "bs" larger chunks of ROM/Flash, should check/fix that). This could have been done much easier with "dd" or "split" or... sorry about that. Flashing using the 32 splitfiles is just too much manual work. I began the work, but after flashing the first part, I caved in due to the thought of doing it 32 times was just too horrifically boring. :-) Now that we've established that you have a sane OS (and the 64kB chunks), I'll just assume it has this little utility called "cat"... you can do (replacing "etc" with the missing files in between): cat flash01.raw flash02.raw flash03.raw etc flash0f.raw > flash_low.raw
cat flash10.raw flash11.raw etc flash1f.raw > flash_high.raw...and program flash_low.raw to $010000-$100000 and flash_high.raw to $100000-$200000. (for any curious win32 users following this, use: copy /b flash01.raw + flash02.raw + etc + flash0f.raw flash_low.raw...instead) Waiting for the cable would still be easier. Few important points (that might be hidden in some corner of forum/wiki/howto) about using "dtvtrans sync": you need to use port 2 for it, you need to have the "reset" wire in the cable and you need wire the DTV reset to port 2 pin 9. But that's (and all of this) is for an another thread (if needed). jsailySorry, will stop derailing this further... keep up the good work and consider releasing the source for the curious |
|
|
|
Post by Espen Skog on Jan 21, 2010 6:55:43 GMT -5
Yes, sorry to hijack this thread with my newbie flashtool questions.
Keep up the great work on the 1541-3-dtv !!! Hope to see more fancy features ...but I cannot quite see how much cooler it can get. I just lvoe the LCD and how I can flip-the-flop with the flick of a swtch...
Espen
|
|
|
|
Post by expertsetup on Apr 22, 2011 3:47:25 GMT -5
I would be delighted to also test a new FW. Sorry for the delay, but I've been busy doing something completely different I'll make some new firmwares for you to test in the next couple of days. Could you PM your email address to me so I can send them directly to you. It's a bugger that I don't have any NTSC DTV or Hummer to test on so you'll need to check it. Hopefully it's just a small offset like it was for the PAL-DTV. The most serious problem in getting it to work was in the acknowledgement routines as the DTV could not pull a line down like a C64... Hey I understand, it can be hard to find time for hobby projects these days. Perhaps there could be some way for me to set the value with a command, might save some effort recompiling and shuffling files back and forth. Not sure if that would entail a large mod or a simple hack. |
|
I skipped going to the main office today because it got too late to drive the 8 hours last night. So I will do it today instead. BUT: Now I had teh chance to flash the 1541-3 and test that new FW you gave. It worked like a charm 
