Nowind, Mac and Linux

Page 5/7
1 | 2 | 3 | 4 | | 6 | 7

By Haohmaru

Paladin (773)

Haohmaru's picture

22-07-2012, 17:25

...I see...

Run nwhostapp as root and there will be rainbows and unicorns! :rnff:

I tried flashing several firmwares into my Nowinds, only the one in nowindlibraries/msxsrc/nowind.rom seems to work properly.

So I can haz the power of easy DSK loadage on my HB-75P! \o/ YAY \o/

HOWEVER...

During flashing of my 2nd Nowind cart there was a slight power failure and...
it won't boot or go into flashing mode anymore so I guess it's fucked now... Sad

Is there any way to recover from a failed flash?

(doesn't mean I'm not happy to have this working *FINALLY* - thanks to all of you who have been of help)

By Manuel

Ascended (18133)

Manuel's picture

22-07-2012, 17:31

There is a way to recover. I think there's a rescue disk. Try nowind_flasher.dsk on a real MSX with the Nowind inserted.

By Haohmaru

Paladin (773)

Haohmaru's picture

22-07-2012, 19:19

Ok so I dug up an old machine with a diskdrive that can write the nowind_flasher.dsk to a disk and hooked up the 8245.

* took nowind_flasher.dsk from nowindlibraries-read-only/disks
* wrote the .dsk to a recently formatted disk
* plugged in 'broken' Nowind in slot 1
* power on 8245 with flasher disk in drive, pressed 'F'
* connected USB, ran 'sudo ./nwhostapp -f ~/nowindlibraries/-read-only/msxsrc/nowind.rom
* ...

So how many hours should I wait before giving up? I started the flash about 10 minutes after the previous post in this thread and still absolutely nothing happens. Not even the flash erase has ended.

EDIT: Is there any difference between the nowind_flasher.dsk in the svn and the nowind_flasher.dsk in nwhostapp_v4.2.zip on the Nowind website (apart from the latter being single-sided)?

EDIT2: Ok there is. The nowind_flasher.dsk in svn is v3.0 and the one in the .zip on the website is v2.0.
Both do not seem to work though... Sad

By Manuel

Ascended (18133)

Manuel's picture

22-07-2012, 22:36

I think the flasher disk is supposed to flash from the disk itself. I forgot the details Smile

If your flashing fails, it's no use to actually use the Nowind flash code to flash (that's why you use the flasher disk). So, don't use 'f', it's useless. And it's also no use to use the USB, because the nowind isn't working, remember?

By Edwin

Paragon (1182)

Edwin's picture

23-07-2012, 12:21

I have no experience with aborted flashes, but I suspect Manuel is right.

To make this topic complete, if you don't want to run as root, you can fix this in Linux by creating a file "99-nowind.rules" in /etc/udev/rules.d/ with the following content:

ACTION=="add", BUS=="usb", SYSFS{idVendor}=="0403", SYSFS{idProduct}=="6001", GROUP:="users", MODE:="0660"

This is for Ubuntu Linux. For other distributions you may need to change the group.

By Haohmaru

Paladin (773)

Haohmaru's picture

23-07-2012, 17:29

@Manuel:

No the flasher disk cleary states to connect USB and run the nwhostapp -f nowind.rom command on the pc.
Unless there is a secret flasher disk out there that -does- flash from disk that cannot be found anywhere...

@Edwin:

Ta.

By Sky_hawk

Champion (267)

Sky_hawk's picture

23-07-2012, 18:00

The flashdisk works just like the buildin flashroutine, there are no secret disks needed.The disk from the head subversion repository reports as 'nowind flasher v3.0' or something , this is the latest and only correct version to use.

On the website nowind.nl the flash procedure and trouble shooting /faq describes all this, if there is anything unclear about it, i would love to receive contributions to improve this.

Is short , just start the disk, press 'f', now the msx is ready
Now connect the usb and start nwhostapp -f nowind.rom as root.

Gr,

Jan

By Haohmaru

Paladin (773)

Haohmaru's picture

23-07-2012, 18:36

Well first of all I cannot find a FAQ anywhere on the nowind.nl webpages.

Secondly, I did the 'start disk, press 'f', connect USB and start nwhostapp -f nowind.rom' thing (as mentioned in an earlier post) and it just sits there telling me 'erasing flash' on the pc side and a red screen with white 'xxx'-es on the msx side.
It does not even start the flash erase and I could watch both screens for hours with absolutely nothing happening...

I will try the nowind_flasher.dsk v3.0 method again later this evening, maybe my machines were just tired or something Tongue

By Haohmaru

Paladin (773)

Haohmaru's picture

23-07-2012, 20:06

Ok so the FAQ is in the unfished user manual, which told me absolutely nothing new - basically what has been said in this thread.

Seriously, how long am I supposed to stare at my MSX screen stating 'Nowind Flash Writer (Disk version) v3.0 with a bunch of x-es beneath it and my pc screen stating 'Waiting for chip-erase to complete, this can take several minutes'?

It. Is. Not. Even. Erasing. The. Chip.

By Sky_hawk

Champion (267)

Sky_hawk's picture

23-07-2012, 21:16

So you're saying this thread was amazingly accurate? Great!
If it does not respond after 2 minutes, it is not going to respond ever, there is simple something wrong with either the nowind interface, its usb connection, or its usb host (the linux machine). I think you talked about two different interfaces? Is the other interface working correctly using normal disk-hosting ? (nwhostapp -i some.dsk) ?

you can tried some things:
- try flashing it using a different PC, the USB communication is very timing sensitive, and sometimes I have seen non-working combinations, but only during firmware flashing, during normal operation the protocol has more advanced error-recovery.
- make sure you connect the nowind interface _directly_ to you host pc, not using any usb-hubs. (hubs are ok, once you know it works all right without them, but speed might suffer a little).

- you can try to 'clean' the slot's oxydation, by removing and inserting the interface (or better, some old crappy cartridge some, 4/5 times), not roughly, but insert, remove, insert, remove a few times, I have had good results with this on my older test machines that I don't use a lot.

- you can try a different slot, insert the interface into slot 2 and press '2' on the msx before starting the flashing process, the letter '2' will appear on the screen to indicate it is now expecting usb communication throught slot 2.

Finally, you can 'debug' the usb communication, start 'nwhostapp -twrite' on the host PC, and start a test program on the msx to receive a test-string. (run "nwtest.bas" on the nowind_flasher.dsk)

once both are running you can 'wiggle' usb connectors, and the cartridge a little to see if it has any effect.
I have tracked down many 'dirty' slots liek this.

Greetings,

Jan

Page 5/7
1 | 2 | 3 | 4 | | 6 | 7