I am also facing similar issues of not being able to boot the BBGW. Can you recommend which debugger/cable did you use. I tries searching the net but found only your page.
-Amit On Thursday, 8 September 2016 07:40:50 UTC-4, Stephane Charette wrote: > > The serial debug cable I ordered for my BBGW finally got here. I > downloaded RCN's most recent > build, BBGW-blank-debian-8.5-seeed-iot-armhf-2016-09-04-4gb.img. > > I did see a few errors on the serial console during the installation: > > Creating journal (16384 blocks): done > Writing superblocks and filesystem accounting information: done > Formatting: /dev/mmcblk1 complete > ...cut... > [ 116.630830] 6144 pages cma reserved > [ 116.634355] edma 49000000.edma: edma_prep_slave_sg: Failed to allocate > a descriptor > [ 116.642061] omap_hsmmc 481d8000.mmc: prep_slave_sg() failed > [ 116.647671] omap_hsmmc 481d8000.mmc: MMC start dma failure > [ 117.305788] mmcblk1: unknown error -1 sending read/write command, card > status 0x900 > [ 117.313590] blk_update_request: I/O error, dev mmcblk1, sector 4720640 > [ 117.320212] blk_update_request: I/O error, dev mmcblk1, sector 4720648 > [ 117.326810] blk_update_request: I/O error, dev mmcblk1, sector 4720656 > [ 117.333405] blk_update_request: I/O error, dev mmcblk1, sector 4720664 > > The installation does seem to continue, and it shuts down cleanly at the > end. Not sure if those I/O errors are important. > > When I reboot it without the micro SD card, things seem OK, though I see > this: > > [ 2.169781] PM: Cannot get wkup_m3_ipc handle > [ 2.289107] bone_capemgr bone_capemgr: slot #0: No cape found > [ 2.333102] bone_capemgr bone_capemgr: slot #1: No cape found > [ 2.377098] bone_capemgr bone_capemgr: slot #2: No cape found > [ 2.421098] bone_capemgr bone_capemgr: slot #3: No cape found > Loading, please wait... > fsck: error 2 (No such file or directory) while executing fsck.ext4 for > /dev/mmcblk1p1 > fsck exited with status code 8 > > I'm then presented with the usual login prompt. When I login and run > ifconfig, I see no wireless device. But if I wait a minute or so and try > again, the wireless eventually does show up. > > Is this par for the course? Should I be worried about any of these errors? > > Stéphane > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/20ab747d-543f-4c88-b7ea-7f20f2bc8db5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
