mj-tools-devel Mailing List for MiniJam Tools

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

I am looking for the original software for the minijam and speedloader2
but Innogear seems to have gone belly up. Do you have this software?

Andy

Michael Foord [Mic...@tb...] wrote:
> Is this project still active ?

Not really...I am very dissapointed with the visor, and haven't used it
(or the minijam) in over a year.

> Looking at the slim archive for this group there is a rather negative
> final entry and several caveats on its use !!

Ummm...I think it works fine...

There were bugs in the usb-uhci driver that I hope have been fixed by
now, but mjmmc should work fine, and mj-xfer also works fine to the best
of my meory.

> I am looking to build a standalone mp3 player controlled by my Visor -
> as per http://www.Giantdisc.com and ideally would like to be able to
> upload to my minijam or straight to mmc via an mmc reader/writer
> (preferably one that can be obtained cheaper than the speedloader as I
> live in the UK). The standalone mp3 player is based on a bare-bones
> linux box so as far as I can see this project is my *ONLY* possible
> start point.....

Sounds good.  Good luck!

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

    "The surest way to corrupt a youth is to instruct him to hold in higher
    esteem those who think alike than those who think differently."=20
        -- Nietzsche

Is this project still active ?

Looking at the slim archive for this group there is a rather negative
final entry and several caveats on its use !!

I am looking to build a standalone mp3 player controlled by my Visor -
as per http://www.Giantdisc.com and ideally would like to be able to
upload to my minijam or straight to mmc via an mmc reader/writer
(preferably one that can be obtained cheaper than the speedloader as I
live in the UK). The standalone mp3 player is based on a bare-bones
linux box so as far as I can see this project is my *ONLY* possible
start point.....

Mike

--
This email is confidential & intended solely for the use of the
individual to whom it is addressed.  Any views presented are solely
those of the author & do not necessarily represent those of Towcester
Building Supplies.
If you are not the intended recipient, be advised that
you have received this email in error & that any use, dissemination,
forwarding, printing, or copying of this email is strictly prohibited.
Any files attached to this email will have been checked with virus
software before transmission. However, you should carry out your own
virus check before opening any attachment.
Towcester Building Supplies accepts no liability for any loss or damage
which may be caused by software viruses.

Ste...@ma... [Ste...@ma...] wrote:
>=20
> Hello again Bob;
> Are you a student at the University Wisconsin or a teacher?

I'm a graduate student, working on my Ph.D. in theoretical high-energy part=
icle
physics/phenomenology.  I have been a TA for many courses though.  But
thankfully I'm done with that.  Just research from now on until I graduate.=
  ;)

> Thanks for your feedback, I am definitely going to look into this a lot
> further because I am very interested. I will try to use the application a
> lot more and will let you know the troubles I have (if I have any). I know
> I still have a lot to learn about how your software and the communication
> works.

Great!  I'm sure there are a few bugs lurking.

> I currently got as a engagement gift, the Visor Prism which has a
> rechargeable battery. I understand your pain with the batteries because t=
he
> MiniJam uses a lot, you cannot imagine how much the colour monitor takes!

You'd think with these fancy 0.18 micron processes, and OLED displays, soon
there will be portables on the market that work for a month continuously on=
 one
battery.  Anyway, I've got my fingers crossed.

Do you like the prism?  Can you use it with the minijam reliably?  I imagine
you recharge it every night, right?  That way as long as you don't play mus=
ic
for more than ~2 hours per day, it will never run dead.

With the Visor Deluxe, changing the batteries every day isn't really practi=
cal
(I even have NiMH rechargables).  There's a small but finite probability th=
at
when you remove and replace the batteries, you don't do it fast enough, or =
the
contacts aren't made just right, and it will lose all its memory contents.
Which sucks.

If I use it every day, I have to reinstall everything on it about twice a
month.

> On my own time, in the next week or two I will look into your software and
> talk with the boys at Innogear to find out their stand on Linux with their
> product and I will see what I will come up with.=20

Don't bother.  I had lengthy communications with them, and while they were
initially open to the idea, they wanted me to sign an NDA and agree not to
distribute the source.  So instead I reverse engineered it, only to find an
ABSOLUTELY BRAIN-DEAD filesystem on the mmc.  A monkey could have done bett=
er.
These digital cameras use a DOS FAT filesystem on the mmc.  That would have
been 1000 times smarter, and would have made it a lot easier for 3rd partie=
s to
write software.  With my digital camera I just pop it in, 'mount' it like a
filesystem and use unix 'cp' to get files off it.  It's beautiful.

The format of the MMC is laid out in the 3 structs in mjmmc.h.  Most of the
data fields have been discovered.  Ideally though, a GUI would just call the
mjmmc program, rather than subsuming its code.

If you want to transfer songs over the USB cradle, you'll have to ask Arnim,
since he reverse-engineered the communications protocol it uses.  (mj-xfer
program)

> I do want to get some sort
> of application working because I have to dual boot with windows98 just to
> copy files which I think is absolutely stupid. I want to completely wipe
> out windows from my hard drive.
> thanks for the support and I know for sure I will be emailing you a
> lot..... I guess I will always use this address?
> I think it would be better if you use my home email address
> (st...@or...) because I will do all this "work" on the MiniJam
> from home. (I can check my email from work though)

Please join the mj-tools-devel mailing list (from the sourceforge project
page), and we can communicate through that.  (and in addition, Arnim and an=
yone
else interested can see your ideas)

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

Steven Hartley [ste...@ma...] wrote:
> Hello Bob, I was looking all over the place for software=20
> that will communicate with the MiniJam under Linux and I=20
> stumbled across your great software. I just wanted to know=20
> if there are any plans to build a GUI for the application=20
> to make it more user friendly?
> Please let me know, I'm be interested in helping out.=20

I had not planned on it.  In fact I have stopped using my minijam.  Between=
 the
visor getting grumpy and needing to be reset, or all software reinstalled, =
and
the minijam draining the batteries completely in an hour or so, it's not wo=
rth
the time investment to use.  The visor does not behave very nicely when its
batteries get low, and with the minijam playing, there's no way to know that
the batteries are low.

Anyway, so I haven't used my visor in a while.  Next time around, the handh=
eld
I choose will not be utterly dependent on volatile RAM, will use an OS that=
 has
little more sophistication than DOS, will have color, a rechargable battery,
and 802.11b built-in.  ;)

Also, due to unreliable USB drivers, the tools I wrote are almost useless to
me.  I can't reliably fill the mmc with songs (the app starts to give read
errors...I have to re-run it ~10 times just to fill it with songs), and Arn=
im's
mj-xfer just plain doesn't work with UHCI.

<end rant>

So anyway, I'd be delighted if you wanted to add a GUI for it.  I offer my
support as an "interested spectator".  ;)

Please do some web searches though, there are many other similar GUI projec=
ts.
It would be better to add minijam support for one of these projects than wr=
ite
your own app from the ground up.

Good Luck!
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

So what's the status with UHCI usb hubs?  Has anyone gotten mj-xfer
working with them?

I haven't been using my visor for a month or two.  Got sick of having to
reinstall everything because the minijam sucked the batteries dry.  But
now I'm using NiMH rechargables!

Anyway, UHCI in 2.4.7 seems to be a *little* more stable (*holds
breath*).  I just tried mj-xfer again and I don't see any USB errors, I
can list and delete files.  But when installing a file the visor crashes
with the error:
        FatalError
    ..Src/FttDriver.c
    Line:250, noMansLand1 !=3D 0

     (Reset)

Any ideas on that Arnim?  I'll be out of town for a week and a half, but
when I get back I'll work on it.  What can I send you that would be
useful?  Note that 2.4.7 has your patch to URB_TRANSFER_SIZE =3D 768, so
that's not it...

Looking at Sourceforge's statistics, we've gotten several homepage hits
recently.  You wanna whip up a simple home page for mj-tools while I'm
gone?  Then we should get it indexed by google and other search engines
so people can find the stuff.

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

Hello everybody!

A new release of the mj-tools package has been made. Version 0.2 is
available on the sourceforge server. Changes are few, mainly in the
mjmmc module where Bob's latest sources have been incoorperated (correct
timestamps).
In parallel I have reorganized the CVS repository. It now mirrors the
exact delivery of a release. Further updates should be straight forward
when exporting from the repository.

  Regards

    Arnim

Arnim Laeuger [arn...@gm...] wrote:
> 
> Hi again!
> 
> > Well, I played around with some SCSI_IOCTL_SYNC stuff that doesn't seem
> > to do much.  Currently mjmmc hangs my x86 machine hard, and I took the
> > USB card out of my alpha...
> 
> Apart from the troubles (see below) mjmmc works fine on my machine. No
> crashes or hangs at all.

Good!

> > Attached is the latest version, only some formatting improvements, and
> > the date-in-seconds-since-1904 field.  Haven't had time to play with it
> > much lately.
> 
> It does not compile, there seems to be something missing in mjmmc.h
> (mjmmc_entry has no member date).

Ack, oops.  Attached is the updated header file.

Right now I'm trying to track down a UHCI bug that hangs my machine.
*sigh*

> > So everything works with the Zio?  That's cool.  Any trouble with it?
> > Zio is a USB device, right?
> 
> Yes, the Zio is a USB device. Actually it enumerates as a "supported"
> device from SCM:
> 
> T:  Bus=01 Lev=02 Prnt=13 Port=03 Cnt=01 Dev#= 14 Spd=12  MxCh= 0
> D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs=  1
> P:  Vendor=04e6 ProdID=0006 Rev= 4.04
> S:  Manufacturer=SCM Microsystems Inc.
> S:  Product=eUSB MultiMediaCard Adapter
> S:  SerialNumber=000000000000
> C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
> I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50
> Driver=usb-storage
> E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
> E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
> 
> 
> So far no troubles with kernel drivers or anything else related to USB.

Cool!

> On the other hand mjmmc seems to break the consistency of my MMC. I
> installed the same file twice (with deleting it in between) and had no
> luck. It is always broken in such a way that after ~40 seconds playing
> skips right into the middle of another song. Two or three other songs
> are messed up as well and lead into each other.
> Unfortunately I deleted the initial dump of the card so I am not able to
> recover it with dd :-(

Hmmm, that's bad.  Would it be possible for you to create a "clean" mmc
by: 1) format the mmc, 2) add a bunch of songs using mj-xfer or the
windows software, 3) dump the entire mmc to a file using dd, 4) put the
dump of the mmc somewhere I can get it?  (recall I haven't been able to
use mj-xfer to transfer files yet -- I think it's a UHCI problem...
*sigh*)

The only thing I've ever had to work with was the mmc as it originally
shipped with the minijam.  I've never been able to put songs on it
except with mjmmc, hence, I expect mjmmc isn't perfect.  ;)  For
instance, I still can't get the minijam to display the title/artist of
files.  :(  A dump of a "correct" mmc would help greatly.

> Here is the log from the install run:
[...]
> The listing of the free blocks looks strange to me. There are several
> entries that are the same or have the same end values.

Yes, that's strange.  Whenever I use it, the free block list contains
only one entry, something like: 527-127000.  mjmmc should only ever
leave one big free block, unless you start deleting files from the
middle of the list.

It's a good idea to delete all files on the mmc before installing new
ones, for now.

BTW, how fast is it?  The SanDisk unit should do ~200k/s, but I think
the UHCI driver is messing with me.  (do you see a long pause between
the message "Waiting for close..." and the program exiting?)  Note that
200k/s is limited by the mmc's ability to write, and is considerably
faster than the speed of the "SpeedLoader" sold by InnoGear.  ;)

Cheers,
-- Bob

Bob McElrath (rsm...@st...) 
Univ. of Wisconsin at Madison, Department of Physics

Hi again!

> Well, I played around with some SCSI_IOCTL_SYNC stuff that doesn't seem
> to do much.  Currently mjmmc hangs my x86 machine hard, and I took the
> USB card out of my alpha...

Apart from the troubles (see below) mjmmc works fine on my machine. No
crashes or hangs at all.

> Attached is the latest version, only some formatting improvements, and
> the date-in-seconds-since-1904 field.  Haven't had time to play with it
> much lately.

It does not compile, there seems to be something missing in mjmmc.h
(mjmmc_entry has no member date).

> So everything works with the Zio?  That's cool.  Any trouble with it?
> Zio is a USB device, right?

Yes, the Zio is a USB device. Actually it enumerates as a "supported"
device from SCM:

T:  Bus=01 Lev=02 Prnt=13 Port=03 Cnt=01 Dev#= 14 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=16 #Cfgs=  1
P:  Vendor=04e6 ProdID=0006 Rev= 4.04
S:  Manufacturer=SCM Microsystems Inc.
S:  Product=eUSB MultiMediaCard Adapter
S:  SerialNumber=000000000000
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50
Driver=usb-storage
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=  0ms

So far no troubles with kernel drivers or anything else related to USB.

On the other hand mjmmc seems to break the consistency of my MMC. I
installed the same file twice (with deleting it in between) and had no
luck. It is always broken in such a way that after ~40 seconds playing
skips right into the middle of another song. Two or three other songs
are messed up as well and lead into each other.
Unfortunately I deleted the initial dump of the card so I am not able to
recover it with dd :-(

Here is the log from the install run:

==================================8<======================================

lola:~/tmp/mj-tools-0.1/mjmmc$ ./mjmmc -i /cdrom/0/Apocalyptica\ -\
Path.mp3 
Using device: /dev/sda
volume label: My MMC
size:         63470616 bytes
free space:   4079878 bytes
free space(2):4079372 bytes
numfiles:     16
unknown1:     260 (0x104)
prev:   0       next:   0

Free blocks:
        513-1755, 26707-36745, 124703-50895, 36746-43005, 81782-107082,
90361-107082, 90361-110488, 1756-36745, 124703-50895, 36746-43005,
81782-107082, 90361-107082, 90361-110488, 26707-36745, 124703-50895,
36746-43005, 81782-107082, 90361-107082, 90361-110488, 26707-36745,
124703-50895, 36746-43005, 81782-107082, 90361-107082, 90361-110488,
26707-36745, 124703-50895, 36746-44925, 50896-55671, 65144-68978,
81782-107082, 90361-107082, 90361-110488, 26707-36745, 124703-50895,
36746-43005, 81782-107082, 90361-107082, 90361-110488, 26707-36745,
124703-50895, 36746-43005, 81782-83181, 90326-107082, 90361-107082,
90361-110488, 26707-36745, 124703-50895, 36746-43005, 81782-107082,
90361-107082, 90361-110488, 26707-36745, 124703-50895, 36746-43005,
81782-107082, 90361-107082, 90361-110488, 26707-36745, 124703-50895,
36746-43005, 81782-107082, 90361-107082, 90361-102125, 124703-125436, 
free: 34601292 (4079878)
Title: Path vol. 2
Artist: Apocalyptica feat. Sandra Nas
Couldn't find ID3 Album for /cdrom/0/Apocalyptica - Path.mp3
Couldn't find ID3 Year for /cdrom/0/Apocalyptica - Path.mp3
Couldn't find ID3 Comment for /cdrom/0/Apocalyptica - Path.mp3
Genre: AlternRock (40)
Going to write file...

Writing TOC entry.

Writing header.
Waiting for close...

==================================8<======================================

The listing of the free blocks looks strange to me. There are several
entries that are the same or have the same end values.

Attached you will find the -L output after the install run.

  Ciao

     Arnim
Arnim Laeuger [arn...@gm...] wrote:
> 
> Hello Bob!
> 
> I finally purchased a Zio MMC reader/writer and got mjmmc from the 0.1
> mj-tools release running. Do you have a newer version that I should use?

Well, I played around with some SCSI_IOCTL_SYNC stuff that doesn't seem
to do much.  Currently mjmmc hangs my x86 machine hard, and I took the
USB card out of my alpha...  But I'm pretty sure all my troubles are due
to the UHCI driver, and not mjmmc.  It was working fine not too long
ago.

Attached is the latest version, only some formatting improvements, and
the date-in-seconds-since-1904 field.  Haven't had time to play with it
much lately.

Keep the old one around, just in case.

So everything works with the Zio?  That's cool.  Any trouble with it?
Zio is a USB device, right?

Cheers,
-- Bob

Bob McElrath (rsm...@st...) 
Univ. of Wisconsin at Madison, Department of Physics

Hello Bob!

I finally purchased a Zio MMC reader/writer and got mjmmc from the 0.1
mj-tools release running. Do you have a newer version that I should use?

  Regards

    Arnim

Hello all!

Today I was able to run some short trials on a PC with UHCI hardware.
Sad to say that I was not able to install any files.
The system was an i386 running linux-2.4.3 with UHCI USB hardware (VIA
KT133 chipset).
I was able to download the fileslist once (-t standalone), another -t
left mj-xfer hang and wait forever. After starting MJLoader again,
exactly one filelist could be retrieved and so on.
There was no chance to install a file. Although mj-xfer claimed to
install the file successfully, MJLoader did not show any transfer
activity.

So, I could not make it any further - at least my Visor didn't crash.
We are kind of stuck with UHCI :-(

Sorry for the bad news...

  Arnim

Hello all!

Today I was able to run some short trials on a PC with UHCI hardware.
Sad to say that I was not able to install any files.
The system was an i386 running linux-2.4.3 with UHCI USB hardware (VIA
KT133 chipset).
I was able to download the fileslist once (-t standalone), another -t
left mj-xfer hang and wait forever. After starting MJLoader again,
exactly one filelist could be retrieved and so on.
There was no chance to install a file. Although mj-xfer claimed to
install the file successfully, MJLoader did not show any transfer
activity.

So, I could not make it any further - at least my Visor didn't crash.
We are kind of stuck with UHCI :-(

Sorry for the bad news...

  Arnim

P.S.: The system log:

Apr 26 22:10:08 nausea kernel: visor.c: Handspring Visor: Number of
ports: 2
Apr 26 22:10:08 nausea kernel: visor.c: Handspring Visor: port 1, is for
Generic use and is bound to ttyUSB0
Apr 26 22:10:08 nausea kernel: visor.c: Handspring Visor: port 2, is for
Remote File System use and is bound to ttyUSB1
Apr 26 22:10:08 nausea kernel: usbserial.c: Handspring Visor converter
now attached to ttyUSB0 (or usb/tts/0 for devfs)
Apr 26 22:10:08 nausea kernel: usbserial.c: Handspring Visor converter
now attached to ttyUSB1 (or usb/tts/1 for devfs)
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
547
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
549
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
551
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
553
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
555
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
557
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
559
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
561
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
563
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
565
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
567
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
569
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
571
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
573
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
575
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
577
Apr 26 22:10:14 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
579
...
Apr 26 22:10:16 nausea kernel: usb-uhci.c: interrupt, status 3, frame#
719
Apr 26 22:10:23 nausea kernel: usb.c: USB disconnect on device 5
Apr 26 22:10:23 nausea kernel: usbserial.c: Handspring Visor converter
now disconnected from ttyUSB0
Apr 26 22:10:23 nausea kernel: usbserial.c: Handspring Visor converter
now disconnected from ttyUSB1

Frederic Tessier [te...@my...] wrote:
> Hello Arnim!
>=20
> >
> > Until now I was guessing that Bob's problems are caused by his Alpha
> > platform. Unfortunately there is now another one reporting the same
> > problem. Maybe it is really related to the UHCI driver.
> >
>=20
> You mean Bob run it on an Alpha processor systems? Do you know if they ar=
e=20
> other people are using the minijam tools successfully beside you? It migh=
t be=20
> a good thing to to see if the other people that have it working are on OH=
CI=20
> or UHCI.

I have tried UHCI on alpha and athlon (same errors both ways -- I'm
pretty sure it's a UHCI issue).  Arnim has OHCI on intel.

As far as I know, you're user #3.  ;)  Either that or everyone else has
OHCI or hasn't complained that it doesn't work!  ;)

Right now my USB adapter isn't even in my box right now...I'm trying to
debug some other problems with X 4.0 and kernel 2.4.  I probably won't
get to playing with the USB stuff again soon...

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

Hello Arnim!

>
> Until now I was guessing that Bob's problems are caused by his Alpha
> platform. Unfortunately there is now another one reporting the same
> problem. Maybe it is really related to the UHCI driver.
>

You mean Bob run it on an Alpha processor systems? Do you know if they are 
other people are using the minijam tools successfully beside you? It might be 
a good thing to to see if the other people that have it working are on OHCI 
or UHCI.

>
> Frederic, you wrote that you use SuSE Linux 7.1 - which kernel do you
> use? If it is 2.4.2 or lower, did you apply the patch to visor.c as
> described in the mj-xfer source? The patch is not necessery for 2.4.3
> (and future ones).

At the moment i am on the 2.2.18 kernel! I would like to be running 2.4.0 
(which is also install with SuSE 7.1, but sadly by SoundBlaster crappy 
Vibra16 failed under that!  

Nope i saw that last night while reading your source files ;-), ill first 
need to install the 2.2.18 kernel source.  I try to apply the patch on the 
2.4.0 kernel (the source for it were install), but i am a bit a newbie with 
those kernel recompiling stuff 8-(.  How can i recompile just the visor 
kernel modules? I dont really wanna recompile the whole kernel.

> If this does not help, and one of you would like to experiment, here is
> a proposal for another patch. Looks as if you both are stuck with the
> problem that MJLoader does not accept packetized data from the host. So
> some experimenting could clarify things.

Ill try to apply this patch first and let you know when ill be running the 
new revised visor modules.  Well if i remember they are some issue with 
packet stuff with the UHCI compare to the OHCI (they were some explanation on 
usb.org forum about it).

> I looked through usb-uhci.c and there is some code that I cannot
> correlate to usb-ohci.c. In function uhci_submit_bulk_urb() there is a
> mechanism to split the transferred data into smaller packets. The code
> in question is in lines 892/893 for kernel 2.4.3:
>
>   if (pktsze > maxsze)
>     pktsze = maxsze;
>
> Maybe if you just comment out these two lines and recompile/reload the
> module. Perhaps this will temporarily work around the problem, but be
> careful. If I find me an UHCI card/mobo I could try and do some debug
> work myself :-(
>

Ill try this later if the first solution doesnt improve anything.

>   Good luck and backup well!
>

Thanks again for your collaboration, hopefully by helping each other we 
should be able to get ride of this annoying bugs (yuk yuk today i have to use 
Windows2000 to upload some new mp3 on my innogear!)

>     Arnim
>
>
>
> P.S: The documentation in the tar.gz distribution is quite short. You
> could have a look at the README in the CVS tree which is not yet
> distributed.

This is what i did ;-), since the readme in your dir was only saying "use the 
force Luke" hehehe ;-).

Fred

Hello all!

> > >Armin wrote mj-xfer, and he has a OHCI, and it seems to work fine for
> > >him.  I have UHCI and I see exactly what you describe above.

Until now I was guessing that Bob's problems are caused by his Alpha
platform. Unfortunately there is now another one reporting the same
problem. Maybe it is really related to the UHCI driver.

> > Ill do some another test tonight, maybe add some debug in the mj-xfer
> > could help!  So you are stuck like me by not be able to transfer your
> > music into the Minijam unless you boot up windows right?

Frederic, you wrote that you use SuSE Linux 7.1 - which kernel do you
use? If it is 2.4.2 or lower, did you apply the patch to visor.c as
described in the mj-xfer source? The patch is not necessery for 2.4.3
(and future ones).
If this does not help, and one of you would like to experiment, here is
a proposal for another patch. Looks as if you both are stuck with the
problem that MJLoader does not accept packetized data from the host. So
some experimenting could clarify things.
I looked through usb-uhci.c and there is some code that I cannot
correlate to usb-ohci.c. In function uhci_submit_bulk_urb() there is a
mechanism to split the transferred data into smaller packets. The code
in question is in lines 892/893 for kernel 2.4.3:

  if (pktsze > maxsze)
    pktsze = maxsze;

Maybe if you just comment out these two lines and recompile/reload the
module. Perhaps this will temporarily work around the problem, but be
careful. If I find me an UHCI card/mobo I could try and do some debug
work myself :-(

  Good luck and backup well!

    Arnim

P.S: The documentation in the tar.gz distribution is quite short. You
could have a look at the README in the CVS tree which is not yet
distributed.

UHCI/OHCI refers to the hardware chip usb chip you have in your
computer.  If you have OHCI hardware, you need the OHCI driver, if you
hvae UHCI hardware, you need the UHCI driver, you can't switch without
buying a new USB interface card with the different chip on it.

There are two uhci drivers, usb-uhci and uhci.  I've tried them both and
neither works.  :(

 [] wrote:
>=20
> Hello Bob
>=20
> >mj-xfer does the same thing for me.
>=20
> Really? I though that since you were one of the guys working on the
> tools that it would have work at your place.

I wrote mjmmc, the interface for the SanDisk ImageMate, which is much,
much faster.  ;)

> >You aren't using UHCI, by chance?
>=20
> Wow, how did you find out? Yup this is exactly what i use.
>=20
> >Armin wrote mj-xfer, and he has a OHCI, and it seems to work fine for
> >him.  I have UHCI and I see exactly what you describe above.
>=20
> Ah ok, well i try to get the OHCI module to work on my SuSE 7.1 and i
> got an errors (the Visor howto was saying that you had to install 3
> kernel modules, one is visor and the 2 other one are usb-uhci &
> usb-ohci).
>=20
> What is the difference between the 2?=20
>=20
> >I don't know how to fix it (I'm not a USB expert, and I don't have a
> >USB analyzer), but if you can get it working, we'd like to hear about
> >it!  I have problems with many usb devices, and am convinced the UHCI
> >drivers for linux just plain suck, but I'd like to be proven wrong.
>=20
> I am no USB expert either, but do you know the difference between the
> OHCI and UHCI, is there a way i can configure my machine to use the
> OHCI instead? I would really like to use the MiniJam tools under
> Linux! (in worst case scenario i can boot up in Windows2000, but i am
> trying to switch everything i do under Linux ;-)).
>=20
> Ill do some another test tonight, maybe add some debug in the mj-xfer
> could help!  So you are stuck like me by not be able to transfer your
> music into the Minijam unless you boot up windows right?
>=20
> And once that is working right a nice gui would be nice ;-).
>=20
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

Frederic Tessier [te...@my...] wrote:
> Hello there!
>=20
> Well after many attempt i have to say that the mj-xfer=20
> tools doenst work pretty well on my system 8-(.  The only=20
> command i am able to do without getting a crash is mj-xfer=20
> -t (where i get a list of what is on my MMC).  As soon as=20
> i try to install a file it does start the transfer=20
> "Storing blablah" but then crash after a few secs (the=20
> Visor pop up an error that an error occurs in the source=20
> in /src/fft at line xxxx).  And usually i have to reset=20
> the Visor since all the rest of the interface is frozen.

mj-xfer does the same thing for me.

You aren't using UHCI, by chance?

Armin wrote mj-xfer, and he has a OHCI, and it seems to work fine for
him.  I have UHCI and I see exactly what you describe above.

I don't know how to fix it (I'm not a USB expert, and I don't have a USB
analyzer), but if you can get it working, we'd like to hear about it!  I
have problems with many usb devices, and am convinced the UHCI drivers
for linux just plain suck, but I'd like to be proven wrong.

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

Visorcentral (www.visorcentral.com) posted an article recently about
Innogear's speedloader.  I posted a comment in the discussion pointing
people to mj-tools.

Maybe now other people will try it out.  ;)

We've still got 0 downloads at this point!  :(

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics

2001	Jan	Feb	Mar (1)	Apr (7)	May (4)	Jun	Jul (1)	Aug (1)	Sep	Oct	Nov	Dec (2)
2002	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct (2)	Nov	Dec
2003	Jan	Feb	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec

mj-tools-devel Mailing List for MiniJam Tools

mj-tools-devel — Development discussion for mj-tools package