u-boot

https://github.com/MiSTer-devel/Main_MiSTer/wiki

Moderators: Mug UK, Zorro 2, spiny, Greenious, Sorgelig, Moderator Team

THaase
Atari maniac
Atari maniac
Posts: 83
Joined: Mon Oct 16, 2017 8:39 am
Location: Germany

u-boot

Postby THaase » Mon Mar 12, 2018 5:02 pm

Dear Sorgelig,

as I've mentioned http://www.atari-forum.com/viewtopic.php?f=117&t=32736&start=25#p338121 already, I've build up my own Joystick to USB converter for DB9-Joysticks (something for NES/SNES will follow).
Plugging this thing in I was only able to see one js (js0) device.

After searching a little bit on the i-net I've found the solution: http://mheironimus.blogspot.de/2015/09/linux-support-for-arduino-leonardo.html
But that means that I've to alter the kernel command line passed by u-boot.

Basically there are 3 possibilities:

Code: Select all

1.)
stop u-boot
change kernel command line
save as default environment


Code: Select all

2.)
use uboot.scr


Code: Select all

3.)
create my own u-boot


As possibility 1 has to be done after every u-boot change (and I will always forget what I've done) this was not an option.
Possibility 2 is nice, nevertheless - can be only done when Linux Environment is set up - yes in my case, but maybe not for others that have the same problem.
Possibility 3 has the same problems as 2 - working Linux environment is needed.

So I've decided for possibility 4 :D

Use uEnv.txt.
I've patched your actual git sources
u-boot-diff.zip
for supporting an existing uEnv.txt in the linux folder of the SD Card.
With that I can easily add some extra kernel parametes just by

Code: Select all

extrakernelcmd=usbhid.quirks=0x1B4F:0x9206:0x040

(exchanged the VID and PID to the Spartfun Pro Micro I'm using).
OK, basically someone can do any other things with this.

So maybe you might thing about taking this over to the 'official' MiSTer u-boot.
You do not have the required permissions to view the files attached to this post.

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 2557
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: u-boot

Postby Sorgelig » Mon Mar 12, 2018 5:19 pm

This is very specific thing and probably no one but you will use it.
You will use these VID/PID. Some other people may use other VID/PID. So, there is no universal solution for this.
So keep it as is for time being - custom build for yourself.

I will keep watching on this problem and if i will find more universal fix then i will integrate it.

THaase
Atari maniac
Atari maniac
Posts: 83
Joined: Mon Oct 16, 2017 8:39 am
Location: Germany

Re: u-boot

Postby THaase » Mon Mar 12, 2018 5:40 pm

Sorry to correct you - but this solution is general.
You've the hid.quirks (or something you need to pass to your environment) in a txt file similar to the MiSTer config file.
So if you have a similar problem (just not using a Sparkfun but a Ardino type) you can just exchange the VID/PID in the text file without compiling something.
Basically you can exchange whatever you like in the bootenvironemt of u-boot.

For sure - you are the maintainer and you have to decide!

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 2557
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: u-boot

Postby Sorgelig » Mon Mar 12, 2018 5:52 pm

Ok. i didn't fully understand your original post.
I will think about easier u-boot environment editing.

Sorgelig
Fuji Shaped Bastard
Fuji Shaped Bastard
Posts: 2557
Joined: Mon Dec 14, 2015 10:51 am
Location: Russia/Taiwan

Re: u-boot

Postby Sorgelig » Mon Mar 12, 2018 5:57 pm

actually, there is already extension for booting script: /linux/u-boot.scr
I just forgot about it.
Maybe it's not as convenient as plain text (it needs pre-conversion), but you can write the whole scenario in u-boot.scr without returning to original script.

THaase
Atari maniac
Atari maniac
Posts: 83
Joined: Mon Oct 16, 2017 8:39 am
Location: Germany

Re: u-boot

Postby THaase » Mon Mar 12, 2018 7:34 pm

Yes - you are right - and I've also seen this before.
But my intention was an easy to edit file - for gererating u-boot.scr you need mkimage thats included in the UBootInstallTools - and that implies a.f.a.i.k a Linux system.
While the txt file can just be edited.
As I said: For me it's not a problem - but maybe for others


Return to “MiSTer”

Who is online

Users browsing this forum: lolof, thgill, zamp and 7 guests