While validating that device serial1 was really a serial port best intimidating phrases

19-Nov-2019 01:25

Using the raspbian-jessie-lite image dd 2016-02-26 (and performing all updates after that), I can't get the serial console working on a RPi 3.

When I put the image in a RPi 2, everything is fine.

while validating that device serial1 was really a serial port-43

There is a forum thread about it and (apparently) someone found a workaround ...

Setting core_freq to 250MHz limit the ARMs to 600MHz. The main clocks are controlled by the settings arm_freq, core_freq, sdram_freq, v3d_freq, isp_freq and h264_freq.

gpu_freq is an alias for the non-ARM clocks that haven't been set explicitly. I started to retrieve all frequency settings on a earlier Pi (using 'vcgencmd get_config int | grep freq'), copying all to to overrule the new defaults, and the problem was gone.

Although these blocks are the same in this example, the addresses can differ between z_load and u_load.: 2015-06-19 AM DEBUG: boot_cmds(after preprocessing): ['setenv autoload no', u"setenv kernel_addr_r '0x4002000000'", u"setenv initrd_addr_r '0x4004000000'", u"setenv fdt_addr_r '0x4003000000'", u"setenv loadkernel 'tftp $ tmplv_w Qe/u Image_1.11'", "setenv loadinitrd 'tftp $ '", u"setenv loadfdt 'tftp $ tmplv_w Qe/mustang.dtb_1.11'", u"setenv nfsargs 'setenv bootargs root=/dev/nfs rw nfsroot=10.3.2.1:/var/lib/lava/dispatcher/tmp/tmplv_w Qe/tmprhr AXO,tcp,hard,intr panic=1 console=tty S0,115200 earlyprintk=uart8250-32bit,0x1c020000 debug ip=dhcp'", u"setenv bootcmd 'dhcp; setenv serverip 10.3.2.1; run loadkernel; run loadinitrd; run loadfdt; run nfsargs; bootm $ - $'", 'boot'] command is present in the U-Boot version on the board and that it works with z Image kernels.

The eventual templates will exist on the server and can be used to declare the detailed device support so that test writers know in advance what kind of images the device can use.

There is a forum thread about it and (apparently) someone found a workaround ...

Setting core_freq to 250MHz limit the ARMs to 600MHz. The main clocks are controlled by the settings arm_freq, core_freq, sdram_freq, v3d_freq, isp_freq and h264_freq.

gpu_freq is an alias for the non-ARM clocks that haven't been set explicitly. I started to retrieve all frequency settings on a earlier Pi (using 'vcgencmd get_config int | grep freq'), copying all to to overrule the new defaults, and the problem was gone.

Although these blocks are the same in this example, the addresses can differ between z_load and u_load.: 2015-06-19 AM DEBUG: boot_cmds(after preprocessing): ['setenv autoload no', u"setenv kernel_addr_r '0x4002000000'", u"setenv initrd_addr_r '0x4004000000'", u"setenv fdt_addr_r '0x4003000000'", u"setenv loadkernel 'tftp $ tmplv_w Qe/u Image_1.11'", "setenv loadinitrd 'tftp $ '", u"setenv loadfdt 'tftp $ tmplv_w Qe/mustang.dtb_1.11'", u"setenv nfsargs 'setenv bootargs root=/dev/nfs rw nfsroot=10.3.2.1:/var/lib/lava/dispatcher/tmp/tmplv_w Qe/tmprhr AXO,tcp,hard,intr panic=1 console=tty S0,115200 earlyprintk=uart8250-32bit,0x1c020000 debug ip=dhcp'", u"setenv bootcmd 'dhcp; setenv serverip 10.3.2.1; run loadkernel; run loadinitrd; run loadfdt; run nfsargs; bootm $ - $'", 'boot'] command is present in the U-Boot version on the board and that it works with z Image kernels.

The eventual templates will exist on the server and can be used to declare the detailed device support so that test writers know in advance what kind of images the device can use.

New Soft Serial offers a number of improvements over Software Serial: *But see below for an important caveat on multiple instances. The interrupt handler at these rate becomes so lengthy that timer tick interrupts can be starved, causing millis() to stop working during receives.