| 09:13 | topi`> | jnettlet[m]: that's what I was thinking... this means that we must get the SOM without eMMC for development |
| 09:13 | topi`> | jnettlet[m]: does this also prohibit integrating a SDIO-based wifi like the Wilink8 into the Armada SOM? |
| 10:01 | jnettlet[m]> | It depends how you do development. More and more I am recommending embedded customers to run their apps in containers. |
| 10:02 | jnettlet[m]> | Yes sdio WiFi is not an option. Although with the a38x series that really isn't the intended purpose. Too slow. |
| 10:03 | Ke> | jnettlet[m]: could you confirm the type of power source you are using for mcbin and do you modify the u-boot config |
| 10:04 | jnettlet[m]> | Ke: one power source is my own. 18V 2.5A. the other is the one that shipped in the box |
| 10:04 | Ke> | 18V? |
| 10:04 | Ke> | not18W ? |
| 10:05 | Ke> | well 18W 12V would not be 2.5A |
| 10:05 | Ke> | so was it a typo or not? |
| 10:07 | Ke> | I am now at work and have loads of different power sources to try |
| 10:09 | Ke> | I guess things to try now are 1) u-boot memtest 2) u-boot with zeroing dram 3) different power sources |
| 10:12 | jnettlet[m]> | no 18V...although I was wrong this power supply was 16V 3.5A |
| 10:13 | jnettlet[m]> | I also have a 12V 5A, and the one that came in the box 12V 2.5A |
| 10:22 | Ke> | jnettlet[m]: so setting higher voltage for the board is safe, I guess it just heats up the regulators? |
| 10:24 | jnettlet[m]> | Ke: I am quite certain that this uses the same circuit protection that our ClearFog line does. Although I will double check that with the hardware designers. It does support the same POE modules which require support of up to 45V I believe. |
| 10:24 | jnettlet[m]> | although the "official" docs say only a 12V source |
| 10:25 | Ke> | I guess I could also try 13.5V from my power supply to see, if it would make a difference |
| 10:36 | jnettlet[m]> | Ke: you are still just running the board and memory? |
| 10:37 | Ke> | sure |
| 10:37 | Ke> | well SD card also |
| 12:10 | jnettlet[m]> | just as there have been some questions. This is the default versions that came on my latest board. https://pastebin.com/ftjSU8WC |
| 12:10 | jnettlet[m]> | obviously I have a 16GB non-ECC chip in this board |
| 12:13 | Ke> | wow 17.02 is anciend |
| 12:13 | Ke> | ancient |
| 12:14 | jnettlet[m]> | yep, this is just for posterity's sake |
| 12:15 | suihkulokki> | jnettlet[m]: thanks |
| 12:15 | suihkulokki> | what is more complete, mainline u-boot or tianocore port? |
| 12:18 | jnettlet[m]> | that is a good question. I am actually going through the mainline mv-ddr implementation. It appears at least with the a388 implementation that a bug has been introduced. |
| 12:19 | jnettlet[m]> | after ~1000 memory initializations we hit a failure. We the Marvell implementation it made it through 10000 before we ended the test. |
| 12:27 | Ke> | yup, 3A power source did not help |
| 16:41 | vpeter> | jnettlet[m]: is uEnv.txt still supported in mainline u-boot? Or it was dropped. |
| 16:44 | jnettlet[m]> | vpeter: it is supported but you need to define the BOOTCMD in it. If the distro has a generic boot.scr or extlinux it can be used to customize some variables |
| 16:44 | vpeter> | Yes, just googled. |