≡
[00:03:20] <jo0nas> ...or you "git clone https://github.com/igorpecovnik/lib" and check for yourself
[16:53:42] <Antitrack> hello
[16:53:47] <Antitrack> sorry, one more foolish question
[16:54:43] <Antitrack> on the olimex a20 lime2 revision K : I have now latest kernel (4.19.17-sunxi) and latest ubuntu 18.04.1 LTS
[16:55:58] <Antitrack> but now, there is no file /boot/script.bin where I could edit the special parameters which I need, because I need to use the GPIO pins.... ([gpio_para] -> gpio_pin_34=port:PB00<0><default><default><default> )
[16:56:29] <Antitrack> so where do I find the equivalent of script.bin in that new kernel / bootloader ?
[18:30:18] <jo0nas> latest by which definition? I believe latest (stable) Mainline kernel is 4.20.something
[18:31:03] <jo0nas> script.bin relates not to Linux but to U-Boot
[18:31:09] <Antitrack> I told you 4.19.17-sunxi
[18:31:19] <Antitrack> maybe not latest, but new enough ok ?
[18:33:13] <jo0nas> I try help you be more precise in expressing your question - but I shall back out if you are confident that your question is perfect
[18:33:34] <jo0nas> s/perfect/adequate/
[18:38:32] <Antitrack> okay
[18:38:41] <Antitrack> what else do you need to know?
[18:51:35] <jo0nas> it is not what I need - it is what others might find helpful clues to help you
[18:53:01] <jo0nas> personally I use Linux and U-Boot as distributed by Debian, and am unaware of any problems with those
[18:54:07] <jo0nas> other flavors may work equally well or better - but since your question is about something broken I guess it makes sense to be specific on what it is you experience is broken
[18:55:37] <jo0nas> I don't know what "4.19.17-sunxi" really means - I guess it means "Mainline Linux 4.19.17 + some patches from someone, based off of the ancient 4.14 dump by Allwinner"
[18:55:51] <jo0nas> what is missing to me is who the "someone" is
[18:56:04] <jo0nas> ...if my guess is correct at all
[18:57:08] <jo0nas> but it might be just me - others may understand you perfectly well, recognizing what that identifier really identifies - or perhaps don't need to know such details to help you out
[18:58:10] <adjtm> jo0nas, does even 4.14 for A20 released by allwinner exist?
[18:58:49] <adjtm> good mainline support is for me the main reason to use A20 in general and A20-Lime in particular
[18:59:37] <jo0nas> I don't follow in detail the ancient dumps
[18:59:44] <adjtm> jo0nas, maybe Antitrack doesn't know that this is a community channel and you are not an Olimex staff guy...
[18:59:46] <jo0nas> *something* exist
[19:00:16] <jo0nas> ah - good point
[19:00:53] <adjtm> Antitrack, maybe you could ask Tsvetan directly here or send an email to Olimex with your questions
[19:01:10] <jo0nas> Antitrack: I am not an Olimex employee - I happen to be a Debian developer, but my presence here is simply due to my passion for Olimex devices
[19:03:15] <jo0nas> yes, if the sources you reference are Olimex sources - and you need to use what Olimex defines as "official" (not what Ubuntu or Debian or Linus Torvalds or anyone else calls "official") then yes, it is a good idea to contact Tsvetan (the owner of Olimex) directly - or perhaps use the company support email, that is sometimes faster
[19:04:17] <jo0nas> if I recall correctly, the support email is not prominently listed at the website, but is mentioned on the invoice when you buy stuff from Olimex
[20:48:31] <Antitrack> ok
[20:48:46] <Antitrack> I did write a email to support at olimex dot com
[20:48:52] <Antitrack> no answer so far
[20:49:10] <Antitrack> also , no booting from emmc possible in revision K of my board, olimex A20 Lime2
[20:49:30] <Antitrack> any access to the emmc makes the Lime2 simply hang
[20:56:56] <adjtm> Antitrack, I think that Lime2 revision k changed the emmc chip (the new one is available in industrial grade)
[20:57:35] <adjtm> I remember Tsvetan saying that it should work as emmc v4 but not as emmc v5 (or something like that)
[20:57:43] <nedko> it is newer emmc revision and a20 cannot boot directly and needs to go through spi
[20:58:14] <nedko> the boot process needs to go through spi flash, so the emmc v5 can boot
[20:58:57] <adjtm> I have always chosen the boards without nand or emmc, the spi flash is very welcome by the way
[20:59:13] <nedko> the read-only jumper is nice :)
[20:59:50] <adjtm> my Lime2 is very old and my other boards are even older
[20:59:52] <adjtm> :)
[20:59:57] <nedko> i think to get a lime2 with spi flash soon :)
[21:00:21] <nedko> my first one is a micro :)
[21:00:26] <nedko> still operational :)
[21:02:27] <adjtm> my first olimex boards were A13-micro and A10s, I got A20 boards just after that, so A13-micro A10s have only booted a few times :)
[21:09:24] <Antitrack> adjtm: correct, it has a new emmc 5.1 chip and makes problems.
[21:10:04] <Antitrack> adjtm: any try to access the emmc (from a linux booted from sd card) freezes the lime2.
[21:11:12] <Antitrack> also I dont know how to access the GPIO pins now, with kernel 4.17.x
[21:11:24] <Antitrack> i mean 4.19.17-sunxi
[21:11:46] <Antitrack> the GPIO pins.... ([gpio_para] -> gpio_pin_34=port:PB00<0><default><default><default> ) -> was previously edited in script.bin/fex but that file doesnt exist anymore
[21:45:00] <Antitrack> so where do I tell him my gpio pins now?
IRC #olimex 2019-02-15
[00:02:31] <jo0nas> Antitrack: you ask on their forum[00:03:20] <jo0nas> ...or you "git clone https://github.com/igorpecovnik/lib" and check for yourself
[16:53:42] <Antitrack> hello
[16:53:47] <Antitrack> sorry, one more foolish question
[16:54:43] <Antitrack> on the olimex a20 lime2 revision K : I have now latest kernel (4.19.17-sunxi) and latest ubuntu 18.04.1 LTS
[16:55:58] <Antitrack> but now, there is no file /boot/script.bin where I could edit the special parameters which I need, because I need to use the GPIO pins.... ([gpio_para] -> gpio_pin_34=port:PB00<0><default><default><default> )
[16:56:29] <Antitrack> so where do I find the equivalent of script.bin in that new kernel / bootloader ?
[18:30:18] <jo0nas> latest by which definition? I believe latest (stable) Mainline kernel is 4.20.something
[18:31:03] <jo0nas> script.bin relates not to Linux but to U-Boot
[18:31:09] <Antitrack> I told you 4.19.17-sunxi
[18:31:19] <Antitrack> maybe not latest, but new enough ok ?
[18:33:13] <jo0nas> I try help you be more precise in expressing your question - but I shall back out if you are confident that your question is perfect
[18:33:34] <jo0nas> s/perfect/adequate/
[18:38:32] <Antitrack> okay
[18:38:41] <Antitrack> what else do you need to know?
[18:51:35] <jo0nas> it is not what I need - it is what others might find helpful clues to help you
[18:53:01] <jo0nas> personally I use Linux and U-Boot as distributed by Debian, and am unaware of any problems with those
[18:54:07] <jo0nas> other flavors may work equally well or better - but since your question is about something broken I guess it makes sense to be specific on what it is you experience is broken
[18:55:37] <jo0nas> I don't know what "4.19.17-sunxi" really means - I guess it means "Mainline Linux 4.19.17 + some patches from someone, based off of the ancient 4.14 dump by Allwinner"
[18:55:51] <jo0nas> what is missing to me is who the "someone" is
[18:56:04] <jo0nas> ...if my guess is correct at all
[18:57:08] <jo0nas> but it might be just me - others may understand you perfectly well, recognizing what that identifier really identifies - or perhaps don't need to know such details to help you out
[18:58:10] <adjtm> jo0nas, does even 4.14 for A20 released by allwinner exist?
[18:58:49] <adjtm> good mainline support is for me the main reason to use A20 in general and A20-Lime in particular
[18:59:37] <jo0nas> I don't follow in detail the ancient dumps
[18:59:44] <adjtm> jo0nas, maybe Antitrack doesn't know that this is a community channel and you are not an Olimex staff guy...
[18:59:46] <jo0nas> *something* exist
[19:00:16] <jo0nas> ah - good point
[19:00:53] <adjtm> Antitrack, maybe you could ask Tsvetan directly here or send an email to Olimex with your questions
[19:01:10] <jo0nas> Antitrack: I am not an Olimex employee - I happen to be a Debian developer, but my presence here is simply due to my passion for Olimex devices
[19:03:15] <jo0nas> yes, if the sources you reference are Olimex sources - and you need to use what Olimex defines as "official" (not what Ubuntu or Debian or Linus Torvalds or anyone else calls "official") then yes, it is a good idea to contact Tsvetan (the owner of Olimex) directly - or perhaps use the company support email, that is sometimes faster
[19:04:17] <jo0nas> if I recall correctly, the support email is not prominently listed at the website, but is mentioned on the invoice when you buy stuff from Olimex
[20:48:31] <Antitrack> ok
[20:48:46] <Antitrack> I did write a email to support at olimex dot com
[20:48:52] <Antitrack> no answer so far
[20:49:10] <Antitrack> also , no booting from emmc possible in revision K of my board, olimex A20 Lime2
[20:49:30] <Antitrack> any access to the emmc makes the Lime2 simply hang
[20:56:56] <adjtm> Antitrack, I think that Lime2 revision k changed the emmc chip (the new one is available in industrial grade)
[20:57:35] <adjtm> I remember Tsvetan saying that it should work as emmc v4 but not as emmc v5 (or something like that)
[20:57:43] <nedko> it is newer emmc revision and a20 cannot boot directly and needs to go through spi
[20:58:14] <nedko> the boot process needs to go through spi flash, so the emmc v5 can boot
[20:58:57] <adjtm> I have always chosen the boards without nand or emmc, the spi flash is very welcome by the way
[20:59:13] <nedko> the read-only jumper is nice :)
[20:59:50] <adjtm> my Lime2 is very old and my other boards are even older
[20:59:52] <adjtm> :)
[20:59:57] <nedko> i think to get a lime2 with spi flash soon :)
[21:00:21] <nedko> my first one is a micro :)
[21:00:26] <nedko> still operational :)
[21:02:27] <adjtm> my first olimex boards were A13-micro and A10s, I got A20 boards just after that, so A13-micro A10s have only booted a few times :)
[21:09:24] <Antitrack> adjtm: correct, it has a new emmc 5.1 chip and makes problems.
[21:10:04] <Antitrack> adjtm: any try to access the emmc (from a linux booted from sd card) freezes the lime2.
[21:11:12] <Antitrack> also I dont know how to access the GPIO pins now, with kernel 4.17.x
[21:11:24] <Antitrack> i mean 4.19.17-sunxi
[21:11:46] <Antitrack> the GPIO pins.... ([gpio_para] -> gpio_pin_34=port:PB00<0><default><default><default> ) -> was previously edited in script.bin/fex but that file doesnt exist anymore
[21:45:00] <Antitrack> so where do I tell him my gpio pins now?
