≡
[16:19:11] <norton> I got to the olimage again and I think U-boot detects my board wrongly
[16:19:21] <norton> What U-Boot says:
[16:19:21] <norton> ID: A20-OLinuXino-LIME Rev.A
[16:19:21] <norton> SN: 00000000
[16:19:21] <norton> MAC: FF:FF:FF:FF:FF:FF
[16:19:30] <norton> what I actually have: A20-OLinuXino-MICRO Rev. G
[19:28:19] <norton> I thought that SN: 0000 and MAC: FF:FF was invalid
[19:28:23] <norton> but apparently it's okay
[19:44:26] <norton> I changed EEPROM data with `olinuxino config write ...` and now Olimage has SATA support and GPIO probably too
[19:44:29] <norton> still no sound though
[19:45:01] <norton> I'll check sound with my headphones later, rn I have other issue - I used olinuxino-sd-to-sata script
[19:45:07] <norton> it said `no spi flash found` at the end
[19:45:40] <norton> PC doesn't boot without Micro SD. With micro sd, it boots and / is mounted on micro sd.
[19:46:56] <norton> the file system on SATA SSD partition is present.
[19:49:30] <norton> As I understand, it's not possible to boot completely from SSD? I checked boot.scr file and there's only three lines - `loaded from SD`, `loaded from eMMC (micro sd)` and `loaded from SPI`.
[19:49:52] <norton> Found this forum post: https://www.olimex.com/forum/index.php?topic=8627.0
[19:52:41] <norton> How do I change rootfs to /dev/sda1?
[19:53:08] <clarity> you have to look at the uboot environment
[19:53:20] <clarity> it will pass a command line to the kernel, which specifies rootfs
[19:53:29] <norton> uEnv.txt?
[19:53:54] <clarity> env print (or env print all or something like that) in uboot
[19:54:10] <clarity> Maybe it is stored in uEnv.txt, I don't know
[20:18:14] <norton> I forced U-boot to run from scsi0 target with `env edit distro_bootcmd`.. originally it was iterating through various targets, and emmc was ahead in order so it booted from emmc
[20:18:35] <norton> I also could just erase emmc filesystem and it would automatically boot from scsi0 target because emmc target would be unsuccesful
[20:37:46] <clarity> courier just stopped by, now I also have olinuxino sbc
[20:37:49] <clarity> though not a20-micro
[21:18:15] <norton> how do I know if my board has SPI?
[21:18:21] <norton> it's not listed there
[21:18:21] <norton> https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-MICRO/resources/A20-OLinuXino-Micro.pdf
[21:18:49] <norton> In the 3.1 and 3.2 sections
[21:41:10] <clarity> every a20 board has spi
[21:41:24] <clarity> whether it is connected to anything is a different matter
[21:48:59] <clarity> https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-MICRO
[21:49:10] <clarity> Find the schematic for your revision, then look for the part you are interested in
[21:51:00] <clarity> I don't know if they label the variant on the board somewhere
[21:51:18] <clarity> If you have the original box, it should have the full name including variant
[21:54:02] <nedko> there is revision on the pcb
[21:54:51] <nedko> my first one is micro rev.C
[21:55:03] <nedko> this is 10+ years ago
[22:01:10] <clarity> nedko if you can locate and tell norton where the SPI flash is, that could be helpful
[22:01:18] <clarity> (U25 in Rev M schematic)
[22:01:28] <clarity> W25Q128
[22:02:11] <norton> Mine is Rev. G
[22:02:12] <clarity> I don't have the board and photos online are too small to read :( Maybe I could open the board file but I need to install some software for that and no time right now
[22:02:35] <norton> though U-boot currently detects it as Rev. C
[22:02:48] <norton> i should write eeprom again, yeah
[22:04:45] <clarity> Hmmm
[22:05:08] <clarity> Rev G doesn't have spi flash option
[22:05:12] <clarity> Oh wait
[22:05:20] <clarity> I'm reading lime2 revisions, sorry
[22:05:47] <clarity> Unfortunately that appears to be true for MICRO as well
[22:06:09] <clarity> Rev K >21. SPI Flash for enabling other booting option was added! It required several other components to be added around it too;
[22:06:46] <clarity> Do you have emmc norton?
[22:07:39] <clarity> Hmmm.. G is also without eMMC
[22:08:34] <clarity> That sucks! It may have nand flash, but I have no idea how well that is supported
[22:09:46] <clarity> I have never used nand flash and can't really help with that.. if you can't get it working, you're probably stuck with bootloader on sd card
[22:19:38] <norton> there's no NAND flash
[22:19:50] <norton> there's only eMMC port
[22:19:55] <norton> no built-in emmc
[22:21:41] <norton> I'm not sure how to read "REVISION CHANGES.txt"
[22:21:49] <norton> in what order they go?
[22:22:09] <norton> G is first there, so does it mean my board is from the latest revision? or the oldest?
[22:23:49] <norton> yeah I think G is the oldest
[22:24:16] <norton> nand flash is not about revision, it's a variant of the board. as i understand there's also a variant with built-in eMMC (micro sd?)
[22:24:50] <norton> My board is just MICRO, without nand or built-in emmc. I have emmc port, sd card port (mmc_2). that's it.
[22:43:47] <norton> guys
[22:44:00] <norton> i managed to fix everything except of sound
[22:44:09] <norton> there's no sound. what do?
[22:47:48] <norton> `aplay -l` lists `card 0: sun4i-codec, device 0: CDC PCM Codec-0
[23:12:58] <clarity> did you check volumes with alsamixer or something like that?
[23:13:09] <clarity> do you have a gui? does the system have pulseaudio or pipewire? what are you using to test sound?
[23:13:52] <clarity> btw
[23:14:04] <clarity> yesterday you said it didn't react in u-boot when you pressed a key, how did you solve that?
[23:15:11] <norton> 1. it varies from image to image. On U-boot 2023 it wasn't working at all.
[23:15:30] <norton> 2. on olimage it didn't work, but after first/second boot it started working
[23:15:49] <norton> you can see u-boot 2023 in debian official installer for example.
[23:16:01] <norton> olimage has u-boot 2021
[23:16:28] <norton> yep i have xfce4. i used speaker-test. i have alsa installed.
[23:16:45] <norton> it's kinda sus that it says sun4i codec...
[23:16:58] <norton> A20 is sun7i right? :-)
[23:18:05] <clarity> it is but sometimes they share logic
[23:18:23] <norton> yep maybe it's okay, who knows
[23:18:32] <clarity> you would have to check the dts and driver to be sure
[23:18:40] <norton> wdym
[23:19:01] <norton> it's olimage, it detects board automatically from the eeprom and gets needed dtbs
[23:19:16] <clarity> dt tells you which compatible string it's configured with, that in turn reveals which driver is going to load
[23:19:28] <norton> also there's no dtb on limage
[23:19:40] <norton> only kernel.itb and some .its file, i forgot.
[23:19:41] <clarity> and then looking at the driver (or adjacent drivers) would probably reveal whether it is supposed to work on that chip
[23:19:45] <clarity> itb has the dtbs
[23:19:52] <norton> i'm not sure how to work with itb
[23:20:08] <norton> like i saw dtb compile tutorial and on output you get .dtb, not .itb ?
[23:20:15] <clarity> yes
[23:20:34] <clarity> There was another step which should build the itb
[23:20:57] <norton> can you point me to the wiki/docs/something
[23:20:58] <clarity> Also known as FIT image.. don't ask why there are so many names for the same thing
[23:22:11] <clarity> I can't remember where the olimex build steps were linked, you found them a day or two ago
[23:22:42] <clarity> In general fit is built with mkimage but I can't remember whether it can extract them too or if there's another tool for that
[23:22:51] <clarity> (binwalk probably would work in a pinch)
[23:26:44] <norton> https://www.olimex.com/forum/index.php?topic=7745.0
[23:27:01] <norton> my aplay -l is basically the same
[23:28:05] <norton> and I applied this fix: https://linux-sunxi.org/Audio_Codec#Troubleshooting
[23:28:07] <norton> still no luck
[23:30:25] <norton> https://www.olimex.com/forum/index.php?topic=9086.0
[23:32:57] <clarity> I just booted my new lime2 for the first time
[23:53:39] <norton> OH SHIT
[23:53:57] <norton> https://archlinuxarm.org/forum/viewtopic.php?t=10415
[23:54:25] <norton> " raise the "Power Amplifier" to hear something"
[23:54:28] <norton> that helped me
[23:54:32] <norton> power amp was on zero
[23:56:05] <norton> thank god forums exist cause they are searchable
[23:56:30] <norton> There's a ton of information on IRC and Telegram but it's all closed and non-indexed
IRC #olimex 2023-11-29
[16:17:28] <norton> Hello guys[16:19:11] <norton> I got to the olimage again and I think U-boot detects my board wrongly
[16:19:21] <norton> What U-Boot says:
[16:19:21] <norton> ID: A20-OLinuXino-LIME Rev.A
[16:19:21] <norton> SN: 00000000
[16:19:21] <norton> MAC: FF:FF:FF:FF:FF:FF
[16:19:30] <norton> what I actually have: A20-OLinuXino-MICRO Rev. G
[19:28:19] <norton> I thought that SN: 0000 and MAC: FF:FF was invalid
[19:28:23] <norton> but apparently it's okay
[19:44:26] <norton> I changed EEPROM data with `olinuxino config write ...` and now Olimage has SATA support and GPIO probably too
[19:44:29] <norton> still no sound though
[19:45:01] <norton> I'll check sound with my headphones later, rn I have other issue - I used olinuxino-sd-to-sata script
[19:45:07] <norton> it said `no spi flash found` at the end
[19:45:40] <norton> PC doesn't boot without Micro SD. With micro sd, it boots and / is mounted on micro sd.
[19:46:56] <norton> the file system on SATA SSD partition is present.
[19:49:30] <norton> As I understand, it's not possible to boot completely from SSD? I checked boot.scr file and there's only three lines - `loaded from SD`, `loaded from eMMC (micro sd)` and `loaded from SPI`.
[19:49:52] <norton> Found this forum post: https://www.olimex.com/forum/index.php?topic=8627.0
[19:52:41] <norton> How do I change rootfs to /dev/sda1?
[19:53:08] <clarity> you have to look at the uboot environment
[19:53:20] <clarity> it will pass a command line to the kernel, which specifies rootfs
[19:53:29] <norton> uEnv.txt?
[19:53:54] <clarity> env print (or env print all or something like that) in uboot
[19:54:10] <clarity> Maybe it is stored in uEnv.txt, I don't know
[20:18:14] <norton> I forced U-boot to run from scsi0 target with `env edit distro_bootcmd`.. originally it was iterating through various targets, and emmc was ahead in order so it booted from emmc
[20:18:35] <norton> I also could just erase emmc filesystem and it would automatically boot from scsi0 target because emmc target would be unsuccesful
[20:37:46] <clarity> courier just stopped by, now I also have olinuxino sbc
[20:37:49] <clarity> though not a20-micro
[21:18:15] <norton> how do I know if my board has SPI?
[21:18:21] <norton> it's not listed there
[21:18:21] <norton> https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXino-MICRO/resources/A20-OLinuXino-Micro.pdf
[21:18:49] <norton> In the 3.1 and 3.2 sections
[21:41:10] <clarity> every a20 board has spi
[21:41:24] <clarity> whether it is connected to anything is a different matter
[21:48:59] <clarity> https://github.com/OLIMEX/OLINUXINO/tree/master/HARDWARE/A20-OLinuXino-MICRO
[21:49:10] <clarity> Find the schematic for your revision, then look for the part you are interested in
[21:51:00] <clarity> I don't know if they label the variant on the board somewhere
[21:51:18] <clarity> If you have the original box, it should have the full name including variant
[21:54:02] <nedko> there is revision on the pcb
[21:54:51] <nedko> my first one is micro rev.C
[21:55:03] <nedko> this is 10+ years ago
[22:01:10] <clarity> nedko if you can locate and tell norton where the SPI flash is, that could be helpful
[22:01:18] <clarity> (U25 in Rev M schematic)
[22:01:28] <clarity> W25Q128
[22:02:11] <norton> Mine is Rev. G
[22:02:12] <clarity> I don't have the board and photos online are too small to read :( Maybe I could open the board file but I need to install some software for that and no time right now
[22:02:35] <norton> though U-boot currently detects it as Rev. C
[22:02:48] <norton> i should write eeprom again, yeah
[22:04:45] <clarity> Hmmm
[22:05:08] <clarity> Rev G doesn't have spi flash option
[22:05:12] <clarity> Oh wait
[22:05:20] <clarity> I'm reading lime2 revisions, sorry
[22:05:47] <clarity> Unfortunately that appears to be true for MICRO as well
[22:06:09] <clarity> Rev K >21. SPI Flash for enabling other booting option was added! It required several other components to be added around it too;
[22:06:46] <clarity> Do you have emmc norton?
[22:07:39] <clarity> Hmmm.. G is also without eMMC
[22:08:34] <clarity> That sucks! It may have nand flash, but I have no idea how well that is supported
[22:09:46] <clarity> I have never used nand flash and can't really help with that.. if you can't get it working, you're probably stuck with bootloader on sd card
[22:19:38] <norton> there's no NAND flash
[22:19:50] <norton> there's only eMMC port
[22:19:55] <norton> no built-in emmc
[22:21:41] <norton> I'm not sure how to read "REVISION CHANGES.txt"
[22:21:49] <norton> in what order they go?
[22:22:09] <norton> G is first there, so does it mean my board is from the latest revision? or the oldest?
[22:23:49] <norton> yeah I think G is the oldest
[22:24:16] <norton> nand flash is not about revision, it's a variant of the board. as i understand there's also a variant with built-in eMMC (micro sd?)
[22:24:50] <norton> My board is just MICRO, without nand or built-in emmc. I have emmc port, sd card port (mmc_2). that's it.
[22:43:47] <norton> guys
[22:44:00] <norton> i managed to fix everything except of sound
[22:44:09] <norton> there's no sound. what do?
[22:47:48] <norton> `aplay -l` lists `card 0: sun4i-codec, device 0: CDC PCM Codec-0
[23:12:58] <clarity> did you check volumes with alsamixer or something like that?
[23:13:09] <clarity> do you have a gui? does the system have pulseaudio or pipewire? what are you using to test sound?
[23:13:52] <clarity> btw
[23:14:04] <clarity> yesterday you said it didn't react in u-boot when you pressed a key, how did you solve that?
[23:15:11] <norton> 1. it varies from image to image. On U-boot 2023 it wasn't working at all.
[23:15:30] <norton> 2. on olimage it didn't work, but after first/second boot it started working
[23:15:49] <norton> you can see u-boot 2023 in debian official installer for example.
[23:16:01] <norton> olimage has u-boot 2021
[23:16:28] <norton> yep i have xfce4. i used speaker-test. i have alsa installed.
[23:16:45] <norton> it's kinda sus that it says sun4i codec...
[23:16:58] <norton> A20 is sun7i right? :-)
[23:18:05] <clarity> it is but sometimes they share logic
[23:18:23] <norton> yep maybe it's okay, who knows
[23:18:32] <clarity> you would have to check the dts and driver to be sure
[23:18:40] <norton> wdym
[23:19:01] <norton> it's olimage, it detects board automatically from the eeprom and gets needed dtbs
[23:19:16] <clarity> dt tells you which compatible string it's configured with, that in turn reveals which driver is going to load
[23:19:28] <norton> also there's no dtb on limage
[23:19:40] <norton> only kernel.itb and some .its file, i forgot.
[23:19:41] <clarity> and then looking at the driver (or adjacent drivers) would probably reveal whether it is supposed to work on that chip
[23:19:45] <clarity> itb has the dtbs
[23:19:52] <norton> i'm not sure how to work with itb
[23:20:08] <norton> like i saw dtb compile tutorial and on output you get .dtb, not .itb ?
[23:20:15] <clarity> yes
[23:20:34] <clarity> There was another step which should build the itb
[23:20:57] <norton> can you point me to the wiki/docs/something
[23:20:58] <clarity> Also known as FIT image.. don't ask why there are so many names for the same thing
[23:22:11] <clarity> I can't remember where the olimex build steps were linked, you found them a day or two ago
[23:22:42] <clarity> In general fit is built with mkimage but I can't remember whether it can extract them too or if there's another tool for that
[23:22:51] <clarity> (binwalk probably would work in a pinch)
[23:26:44] <norton> https://www.olimex.com/forum/index.php?topic=7745.0
[23:27:01] <norton> my aplay -l is basically the same
[23:28:05] <norton> and I applied this fix: https://linux-sunxi.org/Audio_Codec#Troubleshooting
[23:28:07] <norton> still no luck
[23:30:25] <norton> https://www.olimex.com/forum/index.php?topic=9086.0
[23:32:57] <clarity> I just booted my new lime2 for the first time
[23:53:39] <norton> OH SHIT
[23:53:57] <norton> https://archlinuxarm.org/forum/viewtopic.php?t=10415
[23:54:25] <norton> " raise the "Power Amplifier" to hear something"
[23:54:28] <norton> that helped me
[23:54:32] <norton> power amp was on zero
[23:56:05] <norton> thank god forums exist cause they are searchable
[23:56:30] <norton> There's a ton of information on IRC and Telegram but it's all closed and non-indexed
