Re: [yocto] Where to look when literally nothing happens?
Thank you for the tip Outback. Since sending my email I’ve actually tried exactly that, I built a fresh image with target raspberrypi-cm3. And the funny thing is, it does the exact same thing. It works fine on the regular pi, and nothing with my cm3 lite. My current suspicion is that this is related to u-boot somehow. I need u-boot because I’d like to use Mender for the OTA updating of my devices. I’m going to see if I can get a stripped down version with just u-boot but without Mender going first. Then maybe I can take it from there. In the mean time all tips and tricks you could give me are very much appreciated. Kind regards, Erik On 1 Nov 2018, 12:51 +0100, Outback Dingo , wrote: On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen wrote: Hello, I’m rather new to embedded software and Yocto. I hope this is the right place to ask. If not I’d appreciate it if someone could point me the right way to do so. I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting and doing things on a regular plain vanilla Raspberry pi 3 board. It boots and over serial console I can log in and do things. But the ultimate target is to run this image on my own board which is built around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ I’ve used so far) works fine on both boards without modification I assumed that this would be the case as well with this image I made myself. But it turns out I was wrong. When I take the image from the build and stick it in my compute module board, literally nothing happens. The boot sequence doesn’t seem to even begin, I get nothing on the serial console, and none of the peripherals like the ethernet ever come to life either. And since nothing happens I really have no idea where to look for a solution. I’m guessing this is a bit of a noob issue? It would be great if someone could point me in a direction to look at. you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit i believe the compute module 3 target is raspberrypi-cm3 you could pretty muuchh do a diff uunder the meta-raspberryypi ffor the differences in whats built Kind regards, Erik Hoogeveen. -- ___ yocto mailing list yocto@yoctoproject.org https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.yoctoproject.org%2Flistinfo%2Fyoctodata=02%7C01%7C%7C0bd7e7fee835429b62b808d63ff0595e%7C84df9e7fe9f640afb435%7C1%7C0%7C636766698851268696sdata=7aiUvFhvNbWvMN8VMy%2BnqlUh9VCAQpnCTMohVpYnmKs%3Dreserved=0 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where to look when literally nothing happens?
On Thu, Nov 1, 2018 at 6:50 PM Outback Dingo wrote: > > On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen > wrote: > > > > Hello, > > > > I’m rather new to embedded software and Yocto. I hope this is the right > > place to ask. If not I’d appreciate it if someone could point me the right > > way to do so. > > > > I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting > > and doing things on a regular plain vanilla Raspberry pi 3 board. It boots > > and over serial console I can log in and do things. > > But the ultimate target is to run this image on my own board which is built > > around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ > > I’ve used so far) works fine on both boards without modification I assumed > > that this would be the case as well with this image I made myself. But it > > turns out I was wrong. > > > > When I take the image from the build and stick it in my compute module > > board, literally nothing happens. The boot sequence doesn’t seem to even > > begin, I get nothing on the serial console, and none of the peripherals > > like the ethernet ever come to life either. > > > > And since nothing happens I really have no idea where to look for a > > solution. I’m guessing this is a bit of a noob issue? It would be great if > > someone could point me in a direction to look at. > > you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit > > i believe the compute module 3 target is raspberrypi-cm3 > > you could pretty muuchh do a diff uunder the meta-raspberryypi ffor > the differences in whats built Yupp see The choices for MACHINE are raspberrypi (BCM2835) raspberrypi0 (BCM2835) raspberrypi0-wifi (BCM2835) raspberrypi2 (BCM2836 or BCM2837 v1.2+) raspberrypi3 (BCM2837) raspberrypi-cm (BCM2835) raspberrypi-cm3 (BCM2837) see https://jumpnowtek.com/rpi/Raspberry-Pi-Systems-with-Yocto.html its a good read on PIs > > > > > Kind regards, > > Erik Hoogeveen. > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Where to look when literally nothing happens?
On Thu, Nov 1, 2018 at 6:33 PM Erik Hoogeveen wrote: > > Hello, > > I’m rather new to embedded software and Yocto. I hope this is the right place > to ask. If not I’d appreciate it if someone could point me the right way to > do so. > > I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting > and doing things on a regular plain vanilla Raspberry pi 3 board. It boots > and over serial console I can log in and do things. > But the ultimate target is to run this image on my own board which is built > around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ > I’ve used so far) works fine on both boards without modification I assumed > that this would be the case as well with this image I made myself. But it > turns out I was wrong. > > When I take the image from the build and stick it in my compute module board, > literally nothing happens. The boot sequence doesn’t seem to even begin, I > get nothing on the serial console, and none of the peripherals like the > ethernet ever come to life either. > > And since nothing happens I really have no idea where to look for a solution. > I’m guessing this is a bit of a noob issue? It would be great if someone > could point me in a direction to look at. you probably built for a raspberrypi3 or raspberrypi3-64 ffor the 64bit i believe the compute module 3 target is raspberrypi-cm3 you could pretty muuchh do a diff uunder the meta-raspberryypi ffor the differences in whats built > > Kind regards, > Erik Hoogeveen. > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Where to look when literally nothing happens?
Hello, I’m rather new to embedded software and Yocto. I hope this is the right place to ask. If not I’d appreciate it if someone could point me the right way to do so. I’m trying to make a Yocto build for a raspberry pi 3. I’ve got it booting and doing things on a regular plain vanilla Raspberry pi 3 board. It boots and over serial console I can log in and do things. But the ultimate target is to run this image on my own board which is built around a Raspberry Pi Compute Module 3 Lite. Since regular Raspbian (what’ I’ve used so far) works fine on both boards without modification I assumed that this would be the case as well with this image I made myself. But it turns out I was wrong. When I take the image from the build and stick it in my compute module board, literally nothing happens. The boot sequence doesn’t seem to even begin, I get nothing on the serial console, and none of the peripherals like the ethernet ever come to life either. And since nothing happens I really have no idea where to look for a solution. I’m guessing this is a bit of a noob issue? It would be great if someone could point me in a direction to look at. Kind regards, Erik Hoogeveen. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
