Mango in Raspberry Pi B+ - Error during initialization

jeremyh

Are you running ma-start.sh as root/su?

FWIW I have been playing around with Mango on a Pi using OpenJDK and it works fine.

pi@mango ~ $ java -version
java version "1.7.0_25"
OpenJDK Runtime Environment (IcedTea 2.3.10) (7u25-2.3.10-1~deb7u1+rpi1)
OpenJDK Zero VM (build 22.0-b10, mixed mode)

zozayagabo

Yes, I am executing sudo ./ma-start.sh

I also, checked using a java version 1.7.0_40 and it keep showing the same error.
Did you edit ma-start file? What version of Mango are you using?

Any other idea?

Gabriel

jeremyh

@zozayagabo said:

Yes, I am executing sudo ./ma-start.sh

I also, checked using a java version 1.7.0_40 and it keep showing the same error.
Did you edit ma-start file? What version of Mango are you using?

Any other idea?

Gabriel

I'm using 2.4.0.

The only thing I can think of is that I usually run:* sudo bash ma-start.sh*
I haven't edited anything at all - it all just worked.

You didn't accidentally download the 'upgrade' zip did you?

zozayagabo

Same thing using the bash instruction.

The file is named mango_automation_2.4.0_full_install.zip . So, it is the right one.

Now, I did have to edit the ma-start file and get rid of the -server in line 45 because I kept getting this error.

Error ocurred during initialization of VM
Server VM is only supported on ARMv7+ VFP

It does not feel like a good practice to edit the executable file. But i could not find another way to get past this error.

Gabriel

zozayagabo

The problem was solved and I could successfully run Mango in my Raspberry Pi B+

Instead of just deleting the -server option in he ma-start.sh, I changed it to -client in line 45 or 53 (depends on the Mango version)
I also, re-transferred the installation file, But this time all the files were already extracted.

One of those, or the combination of them, fixed the problem.

Thanks for your help.
Gabriel

jeremyh

@zozayagabo said:

I also, re-transferred the installation file, But this time all the files were already extracted.

Good that you have solved it and thanks for posting the solution/update.

I wonder if the problem wasn't in the way you were extracting the zip file (causing some permissions issue).
Did you use the linux 'unzip' program?

zozayagabo

Did you use the linux 'unzip' program?

Yes, I was using the Raspbian 'unzip' program. So I extracted first in windows and transferred the already extracted files and Mango ran without issues.

Gabriel

jeremyh

@zozayagabo said:

Did you use the linux 'unzip' program?

Yes, I was using the Raspbian 'unzip' program. So I extracted first in windows and transferred the already extracted files and Mango ran without issues.

That's interesting, I also used unzip in Raspbian, so I'm out of ideas as to why yours didn't work.

phildunlap

I too am unsure why you needed to modify it to -client. Removing -server is necessary, though, as it's a Java optimization flag not supported by ARMv6

I suppose we could modify the start up scripts to check the host architecture and handle this case...