≡
[22:56:24] <norton> Is there a way to effectively search Olimex' IRC archive?
[22:56:42] <norton> https://www.olimex.com/irc
[22:58:46] <clarity> Not that I'm aware of. Of course you can try google site:olimex.com
[22:59:18] <norton> oh yeah
[22:59:21] <norton> forgot about that
[23:00:51] <norton> yeah it's not really efficient :-(
[23:01:14] <norton> also IRC logs are kinda incomplete
[23:02:41] <clarity> I'm sad that tsvetan is no longer here
[23:02:50] <clarity> and many of the others who show up in the logs
[23:02:55] <clarity> it has started to feel like a ghost town :(
[23:03:23] <norton> there are a lot of missing days. I would think that it's the days without any messages, but then I go to some day and there's just "Logging Enabled. Logging disabled". also there's like some discussions without a beginning, if you understand me. as if logging had been interrupted or wasn't enabled when the discussion started.
[23:04:05] <clarity> It is possible that they were days with no activity and somebody responded to something that was asked on a previous day
[23:04:18] <clarity> .. but of course it is always possible that the logger has dropped out too
[23:04:35] <norton> clarity: how could they see these messages if there's no history in irc?
[23:05:00] <clarity> A lot of people, me included, stay connected 24/7
[23:05:00] <norton> is the use of bouncers really that common?
[23:05:08] <norton> oh
[23:05:14] <norton> do you configure some kind of daemon?
[23:05:26] <clarity> No, just irssi
[23:05:53] <norton> I personally suspend my computer at night
[23:06:42] <clarity> You could get a cheap SBC that consumes very little electricity to stay connected 24/7
[23:06:42] <norton> and irc is obviously disconnected. what do you do for that?
[23:06:45] <clarity> (or a VPS)
[23:07:04] <clarity> I run irssi on a small headless & fanless PC that is designed for 24/7 use
[23:07:12] <norton> which pc
[23:07:20] <clarity> shuttle ds437
[23:08:12] <norton> hm
[23:08:49] <norton> I saw in some olimex docs that Olimage is based of Armbian
[23:08:49] <clarity> But irc doesn't require much power, you could use olinuxino for it
[23:09:08] <norton> but I forgot which docs
[23:09:13] <norton> is it [still] true?
[23:10:04] <norton> things like `armbian-config` doesn't work in Olimage. maybe they were stripped out or Olimage isn't based on Armbian [anymore]..
[23:10:14] <norton> i'm thinking what would be better
[23:10:17] <norton> olimage or armbian?
[23:11:50] <clarity> I think olimage is debian based
[23:12:07] <norton> armbian is too
[23:12:12] <norton> oh sorry
[23:12:15] <norton> i misunderstood
[23:12:27] <norton> clarity: hmm.
[23:12:38] <norton> do you know how can I identify my board better?
[23:12:49] <norton> yesterday I just realized that there's nand flash on my board
[23:13:11] <norton> i was reading a20-olinuxino-micro.pdf, looking at top view of the board
[23:13:16] <norton> and the position of nand flash
[23:13:21] <norton> looked on mine and it's there..
[23:13:32] <norton> also I think spi flash is there too!
[23:13:43] <clarity> Oh you did find the location of spi flash?
[23:13:44] <clarity> How?
[23:14:02] <clarity> I thought spi wasn't available at all for your revision but maybe I read the changelog wrong then
[23:14:29] <clarity> What was your revision again?
[23:15:47] <norton> For nand flash I used a magnifying glass and googled the name to be sure, but spi flash is very small, you can't do the same with it... so I'm not sure, but I think it's it. and now I will explain my theory, which I will test in practice today-tomorrow:
[23:17:33] <norton> Since my board has NAND Flash, it means that I have not just A20-OLinuXino-Micro, but a variant with NAND Flash. accordingly, it has a different id in EEPROM, I think 4615....
[23:17:33] <norton> I think that 4615 may have other revisions, and it may have SPI Flash in revision G.
[23:18:41] <norton> https://www.olimex.com/wiki/images/0/08/A20-OLinuXino.jpeg
[23:18:56] <norton> now look at the left of A20 cpu
[23:19:04] <norton> a little gray chip
[23:19:07] <norton> i think it's spi.
[23:20:12] <clarity> Can you read the component number?
[23:20:16] <clarity> Probably Usomething
[23:20:32] <norton> no, it's too small
[23:20:47] <norton> like 1,5 cm
[23:20:58] <clarity> I mean the silk
[23:21:00] <clarity> White text on board
[23:21:16] <norton> i'm not sure where to read it
[23:21:30] <norton> right below the chip?
[23:21:39] <norton> It says "Q3"
[23:22:05] <clarity> Q is usually used for transistors
[23:22:39] <norton> i can upload a picture
[23:25:23] <norton> https://0x0.st/HxeR.jpg
[23:27:01] <clarity> Ok that should be a crystal
[23:27:45] <clarity> Hmmm
[23:30:48] <clarity> Yea Q3 is connected to clk24m_in & out
[23:31:02] <clarity> C100 and C99 are 33pf capacitors on it
[23:34:10] <norton> so what does that mean
[23:34:13] <norton> a crystal
[23:34:52] <clarity> CPU generates clock with it
[23:35:07] <clarity> It'll oscillate at 24MHz
[23:35:24] <norton> can you give a wiki page about these "clock crystals"
[23:35:48] <clarity> https://en.wikipedia.org/wiki/Crystal_oscillator
[23:36:23] <norton> thanks
[23:38:40] <norton> is micro sd == emmc?
[23:39:07] <norton> cause I changed boot parameters in U-boot to boot from "emmc_auto" target and it boots from micro sd
[23:39:12] <clarity> No, micro sd is a detachable card, emmc is a chip soldered on board
[23:39:31] <norton> so yesterday I learned that
[23:39:46] <norton> and also that they have the same flash memory
[23:39:53] <norton> like it's all the same just different interfaces
[23:39:58] <norton> so
[23:40:04] <norton> why does it boot from micro sd then?
[23:40:15] <norton> well there's no "micro_sd" boot target to begin with
[23:40:44] <norton> $ env print boot_targets - fel mmc_auto scsi0 usb0 pxe dhcp
[23:40:51] <norton> oh
[23:40:56] <norton> mmc_auto
[23:41:13] <norton> maybe it means (emmc, sd card, micro sd card) ?
[23:41:23] <norton> so they are all in one target
[23:42:40] <clarity> So I haven't looked at how it works but often emmc and sd cards behave similarly at least looking from userspace, both showing up as /dev/mmcblkN
[23:42:48] <norton> yea
[23:42:56] <norton> so they are both mmc
[23:42:59] <norton> and sd-card
[23:43:02] <clarity> It's possible they are utilizing the same type of hardware peripheral or driver underneath but I'm not 100% sure
[23:43:05] <clarity> The hardware looks different enough
[23:43:23] <norton> well it's always just a nand flash inside
[23:43:26] <norton> as i understand
[23:43:57] <norton> where did you look about "q3 is connected to.."
[23:43:58] <norton> ?
[23:44:28] <clarity> https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-MICRO/2.%20Older%20hardware%20revisions/Hardware%20revision%20G1/A20-OLINUXINO-MICRO_4GB_Rev_G1.pdf
IRC #olimex 2023-12-01
[22:56:11] <norton> Hello guys[22:56:24] <norton> Is there a way to effectively search Olimex' IRC archive?
[22:56:42] <norton> https://www.olimex.com/irc
[22:58:46] <clarity> Not that I'm aware of. Of course you can try google site:olimex.com
[22:59:18] <norton> oh yeah
[22:59:21] <norton> forgot about that
[23:00:51] <norton> yeah it's not really efficient :-(
[23:01:14] <norton> also IRC logs are kinda incomplete
[23:02:41] <clarity> I'm sad that tsvetan is no longer here
[23:02:50] <clarity> and many of the others who show up in the logs
[23:02:55] <clarity> it has started to feel like a ghost town :(
[23:03:23] <norton> there are a lot of missing days. I would think that it's the days without any messages, but then I go to some day and there's just "Logging Enabled. Logging disabled". also there's like some discussions without a beginning, if you understand me. as if logging had been interrupted or wasn't enabled when the discussion started.
[23:04:05] <clarity> It is possible that they were days with no activity and somebody responded to something that was asked on a previous day
[23:04:18] <clarity> .. but of course it is always possible that the logger has dropped out too
[23:04:35] <norton> clarity: how could they see these messages if there's no history in irc?
[23:05:00] <clarity> A lot of people, me included, stay connected 24/7
[23:05:00] <norton> is the use of bouncers really that common?
[23:05:08] <norton> oh
[23:05:14] <norton> do you configure some kind of daemon?
[23:05:26] <clarity> No, just irssi
[23:05:53] <norton> I personally suspend my computer at night
[23:06:42] <clarity> You could get a cheap SBC that consumes very little electricity to stay connected 24/7
[23:06:42] <norton> and irc is obviously disconnected. what do you do for that?
[23:06:45] <clarity> (or a VPS)
[23:07:04] <clarity> I run irssi on a small headless & fanless PC that is designed for 24/7 use
[23:07:12] <norton> which pc
[23:07:20] <clarity> shuttle ds437
[23:08:12] <norton> hm
[23:08:49] <norton> I saw in some olimex docs that Olimage is based of Armbian
[23:08:49] <clarity> But irc doesn't require much power, you could use olinuxino for it
[23:09:08] <norton> but I forgot which docs
[23:09:13] <norton> is it [still] true?
[23:10:04] <norton> things like `armbian-config` doesn't work in Olimage. maybe they were stripped out or Olimage isn't based on Armbian [anymore]..
[23:10:14] <norton> i'm thinking what would be better
[23:10:17] <norton> olimage or armbian?
[23:11:50] <clarity> I think olimage is debian based
[23:12:07] <norton> armbian is too
[23:12:12] <norton> oh sorry
[23:12:15] <norton> i misunderstood
[23:12:27] <norton> clarity: hmm.
[23:12:38] <norton> do you know how can I identify my board better?
[23:12:49] <norton> yesterday I just realized that there's nand flash on my board
[23:13:11] <norton> i was reading a20-olinuxino-micro.pdf, looking at top view of the board
[23:13:16] <norton> and the position of nand flash
[23:13:21] <norton> looked on mine and it's there..
[23:13:32] <norton> also I think spi flash is there too!
[23:13:43] <clarity> Oh you did find the location of spi flash?
[23:13:44] <clarity> How?
[23:14:02] <clarity> I thought spi wasn't available at all for your revision but maybe I read the changelog wrong then
[23:14:29] <clarity> What was your revision again?
[23:15:47] <norton> For nand flash I used a magnifying glass and googled the name to be sure, but spi flash is very small, you can't do the same with it... so I'm not sure, but I think it's it. and now I will explain my theory, which I will test in practice today-tomorrow:
[23:17:33] <norton> Since my board has NAND Flash, it means that I have not just A20-OLinuXino-Micro, but a variant with NAND Flash. accordingly, it has a different id in EEPROM, I think 4615....
[23:17:33] <norton> I think that 4615 may have other revisions, and it may have SPI Flash in revision G.
[23:18:41] <norton> https://www.olimex.com/wiki/images/0/08/A20-OLinuXino.jpeg
[23:18:56] <norton> now look at the left of A20 cpu
[23:19:04] <norton> a little gray chip
[23:19:07] <norton> i think it's spi.
[23:20:12] <clarity> Can you read the component number?
[23:20:16] <clarity> Probably Usomething
[23:20:32] <norton> no, it's too small
[23:20:47] <norton> like 1,5 cm
[23:20:58] <clarity> I mean the silk
[23:21:00] <clarity> White text on board
[23:21:16] <norton> i'm not sure where to read it
[23:21:30] <norton> right below the chip?
[23:21:39] <norton> It says "Q3"
[23:22:05] <clarity> Q is usually used for transistors
[23:22:39] <norton> i can upload a picture
[23:25:23] <norton> https://0x0.st/HxeR.jpg
[23:27:01] <clarity> Ok that should be a crystal
[23:27:45] <clarity> Hmmm
[23:30:48] <clarity> Yea Q3 is connected to clk24m_in & out
[23:31:02] <clarity> C100 and C99 are 33pf capacitors on it
[23:34:10] <norton> so what does that mean
[23:34:13] <norton> a crystal
[23:34:52] <clarity> CPU generates clock with it
[23:35:07] <clarity> It'll oscillate at 24MHz
[23:35:24] <norton> can you give a wiki page about these "clock crystals"
[23:35:48] <clarity> https://en.wikipedia.org/wiki/Crystal_oscillator
[23:36:23] <norton> thanks
[23:38:40] <norton> is micro sd == emmc?
[23:39:07] <norton> cause I changed boot parameters in U-boot to boot from "emmc_auto" target and it boots from micro sd
[23:39:12] <clarity> No, micro sd is a detachable card, emmc is a chip soldered on board
[23:39:31] <norton> so yesterday I learned that
[23:39:46] <norton> and also that they have the same flash memory
[23:39:53] <norton> like it's all the same just different interfaces
[23:39:58] <norton> so
[23:40:04] <norton> why does it boot from micro sd then?
[23:40:15] <norton> well there's no "micro_sd" boot target to begin with
[23:40:44] <norton> $ env print boot_targets - fel mmc_auto scsi0 usb0 pxe dhcp
[23:40:51] <norton> oh
[23:40:56] <norton> mmc_auto
[23:41:13] <norton> maybe it means (emmc, sd card, micro sd card) ?
[23:41:23] <norton> so they are all in one target
[23:42:40] <clarity> So I haven't looked at how it works but often emmc and sd cards behave similarly at least looking from userspace, both showing up as /dev/mmcblkN
[23:42:48] <norton> yea
[23:42:56] <norton> so they are both mmc
[23:42:59] <norton> and sd-card
[23:43:02] <clarity> It's possible they are utilizing the same type of hardware peripheral or driver underneath but I'm not 100% sure
[23:43:05] <clarity> The hardware looks different enough
[23:43:23] <norton> well it's always just a nand flash inside
[23:43:26] <norton> as i understand
[23:43:57] <norton> where did you look about "q3 is connected to.."
[23:43:58] <norton> ?
[23:44:28] <clarity> https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-MICRO/2.%20Older%20hardware%20revisions/Hardware%20revision%20G1/A20-OLINUXINO-MICRO_4GB_Rev_G1.pdf
