EEprom header check fails on 3.19 ish and later kernels

[tmagik]

If I try to use a newer-ish kernel (like the 3.19.3-bone4 version, which I seem to need for a GSM modem to work properly), the init-eMMC-flasher-v3.sh script fails with the following:

• '[' 'xChecking for Valid BBB EEPROM header' '!=' x ']'
• echo 'Checking for Valid BBB EEPROM header' Checking for Valid BBB EEPROM header
• echo 'Checking for Valid BBB EEPROM header' ++ ls '/sys/devices/ocp*/44e0b000.i2c/i2c-0/0-0050/eeprom'
• eeprom_location= [ 10.292591] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 [ 10.292591] [ 10.307525] CPU: 0 PID: 1 Comm: init-eMMC-flash Not tainted 3.19.3-bone4 #1 [ 10.317376] Hardware name: Generic AM33XX (Flattened Device Tree) [ 10.326418] from [ 10.337127] from [ 10.346955] from [ 10.356583] from [ 10.366728] from [ 10.377481] from [ 10.388387] drm_kms_helper: panic occurred, switching back to text console [ 10.398173] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200 [ 10.398173] [ 63.252421] random: nonblocking pool is initialized

Does this require changes to detect some new access method for the eeprom header, or does it require the ocp driver to be ported to 3.19ish kernels?

[RobertCNelson]

That's odd... why is it kernel pancing on the directory ls?

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh#L118

ocp (on-chip-peripherals(OCP)) is part of the device tree spec..

Regards,