@ dcruzer231，
在您的A4版本上，情侣问题，omap4顶部的POP内存显示“ELPIDA”或右侧有一个大圆圈“M”（又名Micron）。
在TI关闭omap4小组并关闭PandaBoard项目后不久，PandaBoard和PandaBoard ES都进行了最后一次运行。
您需要在此处再显示一项更改：
https://www.digikey.com/eewiki/display/linuxonarm/PandaBoard#PandaBoard-PandaBoardA4(with"M"Micronmemory）
更改：./ include / configs / ti_omap4_common.h
/ *使用新的“M”微米存储器评论ES Rev B3或A4的下一行...... * /
#define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS
#ifndef CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS
#define CONFIG_SYS_AUTOMATIC_SDRAM_DETECTION
#define CONFIG_SYS_DEFAULT_LPDDR2_TIMINGS
＃万一
要：./ include / configs / ti_omap4_common.h
/ *使用新的“M”微米存储器评论ES Rev B3或A4的下一行...... * /
/ * #define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS * /
#ifndef CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS
#define CONFIG_SYS_AUTOMATIC_SDRAM_DETECTION
#define CONFIG_SYS_DEFAULT_LPDDR2_TIMINGS
＃万一
然后确保使用“HDMI-1080p”连接器，您应该在视频设备上看到ubuntu启动：
问候，



以下为原文

        @dcruzer231,
Couple questions, on your version of the A4, does the POP memory on top of the omap4 show “ELPIDA” or have a large “M” with a circle on it on the right side (aka Micron).
Shortly after the closing of the omap4 group at TI and the shutdown of the PandaBoard project, there was a last run done on both the PandaBoard and PandaBoard ES. You need to make one more change shown here:
https://www.digikey.com/eewiki/display/linuxonarm/PandaBoard#PandaBoard-PandaBoardA4(with"M"Micronmemory)
Change: ./include/configs/ti_omap4_common.h
/* Comment out next line for ES Rev B3 or A4 with new "M" Micron memory... */#define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS#ifndef CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS#define CONFIG_SYS_AUTOMATIC_SDRAM_DETECTION#define CONFIG_SYS_DEFAULT_LPDDR2_TIMINGS#endifTo: ./include/configs/ti_omap4_common.h
/* Comment out next line for ES Rev B3 or A4 with new "M" Micron memory... *//* #define CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS */#ifndef CONFIG_SYS_EMIF_PRECALCULATED_TIMING_REGS#define CONFIG_SYS_AUTOMATIC_SDRAM_DETECTION#define CONFIG_SYS_DEFAULT_LPDDR2_TIMINGS#endifThen make sure you are using the “HDMI-1080p” connector, and you should see ubuntu bootup on the video device:

Regards,

感谢您的快速回复。
我的董事会有一个ELPIDA
我试过两个HDMI，都没有产生输出。
如果是这种情况，这是创建可启动SD的问题吗？
如果是这种情况，我不确定哪一步导致了这个问题。
我的两个嫌疑人正在构建内核或分区SD卡。
在构建内核时，只有4.9版本可以正常工作，而其他版本的响应时会出现错误，指出基于deb的未知系统。
我能够编译4.9版本。
如果有任何信息我应该包括在内，请告诉我。
对于我的任何无知，我道歉，我对此非常陌生。



以下为原文

        I appreciate your quick response.  My board has an ELPIDA

I have tried both HDMI and neither produce an output. If this is the case is this a problem with creating the bootable SD?
If this is the case I’m not sure which step is causing this problem.  My two suspects are building the kernel or partitioning the SD card.  When building the kernel only the 4.9 version worked as the others responded with an error stating an unknown deb based system.  I was able to compile the 4.9 version supposedly.  If there’s any information I should include to assist please let me know.  My apologies for any ignorance on my end, I am very new at this.

@ dcruzer231，好吧，我在实验室里有一些基于ELPIDA的PandaBoard，明天我会给他们一个快速测试。
我过去遇到的另一个问题是，通过hdmi电缆进行edid检测失败。
作为一种解决方案，我的工作监视器有一个USB集线器，我总是插回到我正在测试的板上，以提供GND路径返回。
请使用来自“未知的基于deb的系统”的日志消息从./build_kernel.sh提供转储，然后我们可以修复构建脚本。
（我们错过了很多基于debian的发行版......）
问候，



以下为原文

        @dcruzer231, okay, i have a few ELPIDA based PandaBoard’s in the lab, i’ll give them a quick test tomorrow.  Another issue I’ve had in the past, edid detection failure over the hdmi cable.  As a work around, my work monitor has a usb hub, that i always plug back into the board i’m testing to provide a GND path return.
Please provide a dump from ./build_kernel.sh with the log message from your “unknown deb based system” then we can fix the build script. (There are quite a few debian based distro’s we miss…)
Regards,

我明天是否可以为我的电路板添加额外接地。
如果有助于故障排除，则仅在为电路板供电时状态2 LED亮起。
当我可以回到它时，我将发布构建脚本的转储。
我正在使用的计算机正在运行Ubuntu 18.04.1 LTS但我稍后会发布完整的转储。



以下为原文

        I’ll see if I can add extra grounding to my board tomorrow.  Only the status 2 LED turns on when powering the board if that helps troubleshooting.  I’ll post the dump of the build script when I can get back to it.  The computer I’m using is running Ubuntu 18.04.1 LTS but I’ll post the full dump later.

@ dcruzer231，在电源插件上，D2只是指示电源，即使没有插入mmc介质。串口上是否有任何显示？
D1 / D2 Led在内核加载之前不会开始闪烁。
D1：心跳，D2：mmc访问。
引导程序有可能无法正确写入。
您应该看到如下所示的内容：
U-Boot SPL 2017.03-dirty（2018年9月25日 -  14:25:52）
OMAP4430-GP ES2.3
试图从MMC1启动
SPL：请为您的主板实施spl_start_uboot（）
SPL：Direct Linux启动不活跃！
U-Boot 2017.03-dirty（2018年9月25日 -  14:25:52 -0500）
CPU：OMAP4430-GP ES2.3
董事会：OMAP4熊猫
I2C：准备好了
DRAM：1 GiB
MMC：OMAP SD / MMC：0
**无法使用mmc 0：1加载env **
使用默认环境
网：找不到以太网。
按SPACE可在2秒内中止自动引导
切换到分区＃0，好的
mmc0是当前设备
在设备0上找到SD / MMC
**找不到文件boot.scr **
**无法识别的文件系统类型**
切换到分区＃0，好的
mmc0是当前设备
扫描mmc 0：1 ...
切换到分区＃0，好的
mmc0是当前设备
在设备0上找到SD / MMC
检查：/uEnv.txt ...
检查：/boot/uEnv.txt ...
50 ms读取20 ms（2 KiB / s）
来自/boot/uEnv.txt的加载环境
使用：dtb = omap4-panda-a4.dtb ...
检查/boot/uEnv.txt中是否设置了uname_r ...
运行uname_boot ...
加载/boot/vmlinuz-4.16.17-armv7-x0.1 ...
6652416字节读取359毫秒（17.7 MiB / s）
loading /boot/dtbs/4.16.17-armv7-x0.1/omap4-panda-a4.dtb ...
读取的80277字节为112毫秒（699.2 KiB / s）
debug：[console = ttyO2,115200n8 root = / dev / mmcblk0p1 ro rootfstype = ext4 rootwait] ...
debug：[bootz 0x82000000  -  0x88000000] ...
## Flattened Device Tree blob at 88000000 
使用fdt blob在0x88000000处启动 
将设备树加载到8ffe9000，结束8ffff994 ...确定
启动内核......
[0.000000]在物理CPU 0x0上引导Linux
[0.000000] Linux版本4.16.17-armv7-x0.1（voodoo @ work-i7）（gcc版本7.3.1 20180425 [linaro-7.3-2018.05修订版d29120a424ecfbc167ef90065c0eeb7f91977701]（Linaro GCC 7.3-2018.05））＃5 SMP PREEMPT Tue
9月25日16:32:09 CDT 2018
[0.000000] CPU：ARMv7处理器[411fc093]版本3（ARMv7），cr = 10c5387d
问候，



以下为原文

        @dcruzer231, at power plug-in, D2 just indicates power, even without the mmc media plugged in.  Does anything show up on the serial port?  D1/D2 Led’s don’t start blinking till the kernel loads.  D1: heartbeat, D2: mmc access.   There is a chance the bootloader wasn’t written correctly.
You should see something like shown:
U-Boot SPL 2017.03-dirty (Sep 25 2018 - 14:25:52)OMAP4430-GP ES2.3Trying to boot from MMC1SPL: Please implement spl_start_uboot() for your boardSPL: Direct Linux boot not active!U-Boot 2017.03-dirty (Sep 25 2018 - 14:25:52 -0500)CPU  : OMAP4430-GP ES2.3Board: OMAP4 PandaI2C:   readyDRAM:  1 GiBMMC:   OMAP SD/MMC: 0** Unable to use mmc 0:1 for loading the env **Using default environmentNet:   No ethernet found.Press SPACE to abort autoboot in 2 secondsswitch to partitions #0, OKmmc0 is current deviceSD/MMC found on device 0** File not found boot.scr **** Unrecognized filesystem type **switch to partitions #0, OKmmc0 is current deviceScanning mmc 0:1...switch to partitions #0, OKmmc0 is current deviceSD/MMC found on device 0Checking for: /uEnv.txt ...Checking for: /boot/uEnv.txt ...50 bytes read in 20 ms (2 KiB/s)Loaded environment from /boot/uEnv.txtUsing: dtb=omap4-panda-a4.dtb ...Checking if uname_r is set in /boot/uEnv.txt...Running uname_boot ...loading /boot/vmlinuz-4.16.17-armv7-x0.1 ...6652416 bytes read in 359 ms (17.7 MiB/s)loading /boot/dtbs/4.16.17-armv7-x0.1/omap4-panda-a4.dtb ...80277 bytes read in 112 ms (699.2 KiB/s)debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait] ...debug: [bootz 0x82000000 - 0x88000000] ...## Flattened Device Tree blob at 88000000   Booting using the fdt blob at 0x88000000   Loading Device Tree to 8ffe9000, end 8ffff994 ... OKStarting kernel ...[    0.000000] Booting Linux on physical CPU 0x0[    0.000000] Linux version 4.16.17-armv7-x0.1 (voodoo@work-i7) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05)) #5 SMP PREEMPT Tue Sep 25 16:32:09 CDT 2018[    0.000000] CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c5387dRegards,

昨天我花了一些时间调试这个，我在启动时看到一个随机的硬锁。
（它也可能是一个糟糕的usb-serial适配器，因为我最终交换了用于串行记录的pc）...但是我将u-boot升级到v2018.09，因此我们现在也启用了你的Spectre变通办法
-boot。
问候，



以下为原文

        I spent some more time debugging this yesterday, i was seeing a random hardlock on bootup. (it also might have been a bad usb-serial adapter, as i ended up swapping the pc i used for serial logging)… But i upgraded u-boot to v2018.09, and thus we also now have the Spectre workarounds enabled in u-boot.
Regards,

所以现在重建内核似乎没有任何障碍。
我没有“未知的基于deb的系统”而构建版本4.10。
现在我遇到的问题是构建uboot。
专门编译它。
这是错误日志：
netlab @netlab-Vostro-460：〜/ u-boot $ make ARCH = arm CROSS_COMPILE = $ {CC} distclean
netlab @netlab-Vostro-460：〜/ u-boot $ make ARCH = arm CROSS_COMPILE = $ {CC} omap4_panda_defconfig 
HOSTCC脚本/ basic / fixdep 
HOSTCC脚本/ kconfig / conf.o 
YACC脚本/ kconfig / zconf.tab.c 
LEX脚本/ kconfig / zconf.lex.c 
HOSTCC脚本/ kconfig / zconf.tab.o 
HOSTLD脚本/ kconfig / conf
＃
#config写入.config
＃
netlab @netlab-Vostro-460：〜/ u-boot $ make ARCH = arm CROSS_COMPILE = $ {CC}
scripts / kconfig / conf --syncconfig Kconfig 
CHK包含/ config.h 
UPD包含/ config.h 
CFG u-boot.cfg 
GEN include / autoconf.mk 
GEN包含/ autoconf.mk.dep 
CFG spl / u-boot.cfg 
GEN spl / include / autoconf.mk 
CHK包括/ config / uboot.release 
UPD包括/ config / uboot.release 
CHK包含/ generated / version_autogenerated.h 
UPD包括/ generated / version_autogenerated.h 
CHK包含/ generated / timestamp_autogenerated.h 
UPD包括/ generated / timestamp_autogenerated.h 
CC lib / asm-offsets.s
cc1：错误：'-march ='开关的错误值（'armv5'）
cc1：注意：'-march ='开关的有效参数是：nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 bonnell atom silvermont slm knl x86-64 eden-x2
nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 btver1 btver2
Kbuild：43：目标'lib / asm-offsets.s'的配方失败了
make [1]：*** [lib / asm-offsets.s]错误1
Makefile：1434：目标'prepare0'的配方失败
make：*** [prepare0]错误2
我使用了v2018.09并且我应用了ompa4补丁。



以下为原文

        So rebuilding the kernel now seems to be working without a hitch.  I built version 4.10 without the “unknown deb based system.”
Now the problem I’m running into is building the uboot.  Specifically compiling it.  Here is the error log:
netlab@netlab-Vostro-460:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC} distcleannetlab@netlab-Vostro-460:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC} omap4_panda_defconfig  HOSTCC  scripts/basic/fixdep  HOSTCC  scripts/kconfig/conf.o  YACC    scripts/kconfig/zconf.tab.c  LEX     scripts/kconfig/zconf.lex.c  HOSTCC  scripts/kconfig/zconf.tab.o  HOSTLD  scripts/kconfig/conf## configuration written to .config#netlab@netlab-Vostro-460:~/u-boot$ make ARCH=arm CROSS_COMPILE=${CC}scripts/kconfig/conf  --syncconfig Kconfig  CHK     include/config.h  UPD     include/config.h  CFG     u-boot.cfg  GEN     include/autoconf.mk  GEN     include/autoconf.mk.dep  CFG     spl/u-boot.cfg  GEN     spl/include/autoconf.mk  CHK     include/config/uboot.release  UPD     include/config/uboot.release  CHK     include/generated/version_autogenerated.h  UPD     include/generated/version_autogenerated.h  CHK     include/generated/timestamp_autogenerated.h  UPD     include/generated/timestamp_autogenerated.h  CC      lib/asm-offsets.scc1: error: bad value (‘armv5’) for ‘-march=’ switchcc1: note: valid arguments to ‘-march=’ switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 bonnell atom silvermont slm knl x86-64 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 znver1 btver1 btver2Kbuild:43: recipe for target 'lib/asm-offsets.s' failedmake[1]: *** [lib/asm-offsets.s] Error 1Makefile:1434: recipe for target 'prepare0' failedmake: *** [prepare0] Error 2I used v2018.09 and I applied the ompa4 patch.

cc1：错误：'-march ='开关的错误值（'armv5'）
cc1：注意：'-march ='开关的有效参数是：nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 bonnell atom silvermont slm knl x86-64 eden-x2
nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 z
这只是意味着，你在另一个终端导出CC ...
https://www.digikey.com/eewiki/display/linuxonarm/PandaBoard#PandaBoard-ARMCrossCompiler:GCC
问候，



以下为原文

        cc1: error: bad value (‘armv5’) for ‘-march=’ switchcc1: note: valid arguments to ‘-march=’ switch are: nocona core2 nehalem corei7 westmere sandybridge corei7-avx ivybridge core-avx-i haswell core-avx2 broadwell skylake skylake-avx512 bonnell atom silvermont slm knl x86-64 eden-x2 nano nano-1000 nano-2000 nano-3000 nano-x2 eden-x4 nano-x4 k8 k8-sse3 opteron opteron-sse3 athlon64 athlon64-sse3 athlon-fx amdfam10 barcelona bdver1 bdver2 bdver3 bdver4 zThis just means, you export’ed CC in another terminal…
https://www.digikey.com/eewiki/display/linuxonarm/PandaBoard#PandaBoard-ARMCrossCompiler:GCC
Regards,

谢谢。
我把它编译好了。
我编译了内核4.10并构建了uboot v2018.09。
但是在运行时，HDMI仍然没有显示。
我同时运行了电源插孔和USB线，但仍然没有。
为了回答上一个问题，我没有检查串口，因为我没有连接到usb线，我需要订购一个。
也许可能是我正在构建SD卡错误？
作为参考，我使用export DISK = / dev / sdb。
我不确定这个改变是否会破坏任何后来的代码。



以下为原文

        Thanks.  I got it compiled.  I compiled kernel 4.10 and built uboot v2018.09.  However when running it still nothing appears through the HDMI. I’ve ran both power jack and usb cord at the same time and still nothing.
To answer a previous question I have not checked the serial port because I do not have a serial to usb cord with me and I would need to order one.
Maybe it could be that I’m building the SD card incorrectly?
For reference I am using export DISK=/dev/sdb.  I’m not sure if that change will mess with any of the later code.

只要你没有通过VMware / VirtualBox /等创建microSD卡，即运行原生linux系统，就应该正确构建SD卡。
D1 LED是否闪烁？
如果是这样我接下来尝试插入一个以太网插孔，你应该能够进入ssh，两个led应该点亮接口以给你一个连接状态。
问候，



以下为原文

        As long as your aren’t creating the microSD cards thru VMware/VirtualBox/etc, aka running off a native linux system, the SD card should be built correctly.
Is D1 LED blinking? If so i’d next try to just plug in an ethernet jack, you should be able to ssh in, both led’s should light up on the interface to give you a connection status.
Regards,

LED 2没有闪烁。
我只是将一个以太网插孔插入电路板。
这似乎已经开始了。
两个LED都亮着，我正在显示。



以下为原文

        LED 2 was not blinking.  I just plugged an ethernet jack into the board.  That seems to have set off the board now.  Both LEDs are on and I’m getting a display.

@ dcruzer231那太疯狂了！
这听起来像;
5伏电源，hdmi监控器和USB连接都有故障。
因此，通过插入以太网电缆，最终设置了适当的GND电平。
问候，



以下为原文

        @dcruzer231 that’s crazy!!!  It sounds like; the 5volt supply, hdmi monitor and usb connection all have a faulty ground.  Thus by plugging in an Ethernet cable, a proper GND level was finally setup.
Regards,

我只是想问你是否知道为什么会这样！
我正在尝试它，现在LED闪烁，我得到一个闪烁的光标但它没有提示登录，直到一个以太网插孔连接到它。
两个不同的pandaboards上的行为相同。



以下为原文

        I was just going to ask you if you know why this is the case!  I’m trying it again and now the LEDs blink and I get a flashing cursor but it doesn’t prompt for login until an ethernet jack is connected to it.  Same behaviour on two different pandaboards.

为了安全起见，我从当地五金店购买了3个LED出口测试仪中的一个，并测试了实验室的插座......
问候，



以下为原文

        To just be safe, I’d grab one of those 3 LED outlet testers from a local hardware store and test the outlet’s in your lab…
Regards,

谢谢，如果我发现它在pandaboard的末端是什么我会报告回来。
再次感谢您对此进行故障排除并更新pandaboard指南。
对此，我真的非常感激。



以下为原文

        Thanks, If I find out that it’s anything on the pandaboard’s end I’ll report back.
Thanks again for troubleshooting this and updating the guide for the pandaboard.  I really appreciate it.