Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hi, > Am 13.03.2018 um 17:58 schrieb cnut: > > Thank you very much Andreas and Nikolaus. > > > Using Nikolaus description of flashing the old uboot via sd card and > afterwards flashing with the latest uboot via sd card did work well. Great that it did work this way. > > > For the record: > When I started the gta04 with the latest rootfs (no usb cable, holding aux > and putting battery in), I did not see a red flashing light. The gta04 screen > showed a menu with SD1, SD2, SD3, SD4, NAND, OFF etc. > > I chose SD1 and after a short green screen, then a white screen, then ca. 3 > minutes loading, I was greeted by LXDE. > Using the hardware validation script via ssh I could see the kernel and uboot > version: > > root@letux:~# ./hw-test > ... > 3 test_kernel ok 4.15.6-letux+ #2081 SMP PREEMPT Sun Feb 25 > 21:44:12 CET 2018 - recommended minimum: 4.10 > ... > 36test_uboot ok U-Boot 2016.11-00249-gc9d20fc foVersion > string of U-Boot in NAND > ... > > > Looking forward to try out qtmoko2. Please send reports. BR and thanks, Nikolaus ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hi, > Am 14.03.2018 um 07:47 schrieb Andreas Kemnade: > > Hi, > > On Mon, 12 Mar 2018 21:56:55 +0100 > "H. Nikolaus Schaller" wrote: > >> Hi Cnut, >> > [...] >> Rebooting didn't show again the issues mentioned above. They seem to be a >> side-effect of migration. >> >> Maybe reflashing the very old boot loader once resets everthing to a state >> that an upgrade to the new one becomes possible or at least does not fail. >> >> So we still don't know why it failed for you, but we seem to have a procedure >> to switch back and forth (using two µSD cards with old and latest >> boot-loader built with current makesd). >> > I guess probably old bootloader flashing new one (because of an > accidiential boot from nand). And then It might have troubles with the > script. > Older uboots e.g. do not recognize the load command, well there should > be error checks. Exactly. It might simply not be possible to solve it better since the shell of u-boot is much less capable than a standard shell + /bin tools. Mainly there is no "which" command... Anyways it is just some ripple on the boot log and appears only once in this special case. So it is not worth finding a fix. > >>> Let's say I have created a sd card with an old boot image and want to test >>> it. See: http://projects.goldelico.com/p/gta04-main/downloads/54/ >>> In the document behind the link is written for "AUX pressed" with "NAND >>> flashed and MMC installed": It does "MLO:MMC". I assume that is the case I >>> need ot flash from sd card. >> >> Yes, so that it does not try to run a broken or bad MLO from NAND. >> >>> Does it mean that I have to >>> - remove usb cable and battery >>> - put the sd card in the gta04 >>> - press and hold aux button >>> - insert battery >>> - and release aux button when something from the sd was loaded (a menu, red >>> screen etc.) >>> Is the assumption correct? >> >> Yes, exactly. >> >> And I recognize that this mail contains a lot of material for a HowTo page. >> Anyone here with a public blog? >> > I think it boils down to follow some instructions exactly to prevent > accidential boots from bad nand contents regardless of whether you do a > rescue from mmc or usb. These instructions do not look as if they have > to be followed exactly in that order. Being shocked because you think > you have a bricked device does not help for that either. So you need to > be calm. Indeed. So far the GTA04 has turned out to be really unbrickable by software. > > The unknown environment is risk factor. But that can be mitigated by > cleaning it during update. The USB-DFU-way does not use environment > from flash, so it should work regardlessly. > It does not even try to > read some content from there, so it just needs to be able to erase and > write to nand. Well, you could also compile a mmc-self-sufficient usb > uboot which does not depend on any information in ram. But this makes it more difficult to understand the list of files and flashing u-boot is no longer copying the same binary as the one that has been used for booting. So I fear that this introduces another potential source of trouble... > > If you know how the boot process works, it is obvious that you have to > follow these instructions in exact that order. > > So I am a bit unsure how to provide the right amount of information > here and what it should be. > > Well, I think I should create a gta04-rescue deb package containing a > script where you have to acknowledge step by step. Yes, this is a very good idea! BR and thanks, Nikolaus ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Thank you very much Andreas and Nikolaus. Using Nikolaus description of flashing the old uboot via sd card and afterwards flashing with the latest uboot via sd card did work well. For the record: When I started the gta04 with the latest rootfs (no usb cable, holding aux and putting battery in), I did not see a red flashing light. The gta04 screen showed a menu with SD1, SD2, SD3, SD4, NAND, OFF etc. I chose SD1 and after a short green screen, then a white screen, then ca. 3 minutes loading, I was greeted by LXDE. Using the hardware validation script via ssh I could see the kernel and uboot version: root@letux:~# ./hw-test ... 3 test_kernel ok 4.15.6-letux+ #2081 SMP PREEMPT Sun Feb 25 21:44:12 CET 2018 - recommended minimum: 4.10 ... 36 test_uboot ok U-Boot 2016.11-00249-gc9d20fc fo Version string of U-Boot in NAND ... Looking forward to try out qtmoko2. Regards cnut ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hi, On Sun, 11 Mar 2018 19:18:04 +0100 Andreas Kemnadewrote: > On Sun, 11 Mar 2018 18:34:23 +0100 > cnut wrote: > > > Hello Nikolaus, > > Hello Andreas, > > > > > > the good news: with the tutorial of Nikolaus, dmesg shows that the > > device is alive... > > [ 2895.846968] usb 1-4: new high-speed USB device number 4 using xhci_hcd > > [ 2895.987845] usb 1-4: unable to get BOS descriptor > > [ 2895.988919] usb 1-4: New USB device found, idVendor=0451, idProduct=d00e > > [ 2895.988932] usb 1-4: New USB device strings: Mfr=33, Product=37, > > SerialNumber=0 > > [ 2895.988941] usb 1-4: Product: OMAP3630 > > [ 2895.988949] usb 1-4: Manufacturer: Texas Instruments > > [ 2898.990793] usb 1-4: USB disconnect, device number 4 > > > > > > usb-starts-uboot shows only: > > # ./usb-start-uboot.sh > > Power on you gta04 with aux button pressed > > Waiting for USB device vendorID=0x451 and productID=0xD009: > > > > > It has to be run *before* powering on the gta04 to start uboot > maybe I should have clearly mention that. That step by step guide was really meant to be done step by step. First thing is to get a running uboot. Transmission can only start in the few seconds when the gta04 appears on the bus. But the script will wait for it to appear. > > dfu-util -l shows not a sign from the gta04 too (no "Found DFU ..."). > > > > > > usb-flash-uboot-gta04.sh does not run too: > > # ./usb-flash-uboot-gta04.sh nand uboot_files/ > > > And that would flash the uboot (and resets the environment). Regards, Andreas pgp8dW3Zk7h6W.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hi Cnut, > Am 11.03.2018 um 18:34 schrieb cnut: > > Hello Nikolaus, > Hello Andreas, > > > the good news: with the tutorial of Nikolaus, dmesg shows that the device is > alive... > [ 2895.846968] usb 1-4: new high-speed USB device number 4 using xhci_hcd > [ 2895.987845] usb 1-4: unable to get BOS descriptor > [ 2895.988919] usb 1-4: New USB device found, idVendor=0451, idProduct=d00e > [ 2895.988932] usb 1-4: New USB device strings: Mfr=33, Product=37, > SerialNumber=0 > [ 2895.988941] usb 1-4: Product: OMAP3630 > [ 2895.988949] usb 1-4: Manufacturer: Texas Instruments > [ 2898.990793] usb 1-4: USB disconnect, device number 4 Fine! > > @Nikolaus: > > Do you by any chance know when you did last time flash the boot loader? > S/N is 6131-0019. Ok, according to our database it was factory tested 2012-10-31 14:17:01 so I assume that this version was originally installed: http://download.goldelico.com/gta04-u-boot/20121030-GTA04-Production/ > I started this thread, because I tried to flash the bootloader (begin of > march 2018). Before, I never flashed the bootloader. Usually upgrades should not be needed, but the device tree kernel mechanism required us to make an exception. The reason is that the kernel is now "univeral" and the boot-loader must know which device it is booting and load the correct DT file into RAM before starting the kernel. This was not available in older boot-loaders where it was even possible to runtime-detect different "board files" and variants by the kernel. > Maybe it helps that QtMokov55 and QtMokov56 were running with the original > bootloader. > Maybe you know the bootloader version, because you assembled the device: The > device was bought by 2013/01 as a complete device from pulster. Because there > were issues with the hardware [1], it was sent to you for repairing. If you > need more information, we should use private mail. > > > > > Maybe the u-boot environment of an old boot loader in NAND flash breaks > > booting a new one and must be reset (which does not work if the device > > does not boot). > OK, seems to be the case here. > Bootloaders before 2013/02 are only available at [2]. But there are no e. g. > MLO files etc. in the directories. There are u-boot.bin, u-bootflash etc. and > makesd. Some of the archived versions seem to be incomplete. At that early ages the packages were edited manually. > Do I have to flash using those makesd versions, which are in same directory > than the u-boot files? > > Did the makesd syntax for creating a sd card change over the time? Well, the makesd from that times was very simple compared to the current one, but it should suffice for making an µSD card. But it might depend on syntax and specialities of older versions of sfdisk and other command line tools. So if you have a recent Ubuntu or Debian, sfdisk will likely fail. Hence let's experiment with latest makesd and make it install the old boot files. With new makesd I tried: ./makesd gta04 -f1 -b http://download.goldelico.com/gta04-u-boot/20121030-GTA04-Production/u-boot.bin -k http://download.goldelico.com/gta04-u-boot/20121030-GTA04-Production/uImage -d none -f2 -m http://download.goldelico.com/gta04-u-boot/20121030-GTA04-Production/modules.tgz This takes the old MLO, u-boot, boot.scr and the old kernel (seems to be a 2.6.32) and no device-tree files to the first partition and the modules to the second one and creates these partitions: 1: fat 5% b:/+http://download.goldelico.com/gta04-u-boot/20121030-GTA04-Production/* k:/+http://download.goldelico.com/gta04-u-boot/20121030-GTA04-Production/uImage dt:/+none r:none m:none c:none 2: ext4 95% b:/+none k:/+none dt:/+none r:http://download.goldelico.com/letux-debian-rootfs/latest-armhf-lxde.tbz m:http://download.goldelico.com/gta04-u-boot/20121030-GTA04-Production/modules.tgz c:http://download.goldelico.com/letux-debian-rootfs/latest-config.tgz 3: none 0% b:/+none k:/+none dt:/+none r:none m:none c:none 4: none 0% b:/+none k:/+none dt:/+none r:none m:none c:none It did boot the very old MLO, the old u-boot, did flash the NAND and did start the 2.6.32 kernel (showing a small Tux on the display). I could also login as root but there was no X11 working (well the X11 config of Debian Jessie + LXDE is not compatible to 2.6.32 kernels). Here is the beginning of the RS232 console log from booting and flashing: tذb$U @D @ Texas Instruments X-Loader 1.4.4ss modified for GTA04 (Oct 30 2012 - 09:50:54) OMAP3630/3730-GP ES2.1 Board detected: GTA04A3 Memory: Micron MCP 256MB/bank Reading boot sector Loading u-boot.bin (270020 bytes) from mmc/sd U-Boot 2011.03-rc1 (Oct 30 2012 - 09:58:13) OMAP3630/3730-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 800 Mhz GTA04 + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 512 MiB MMC: OMAP SD/MMC: 0 Using default environment In:serial Out: serial Err: serial Die ID #003400029ff80163810c1800f00c Hit any key to
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
On Sun, 11 Mar 2018 18:34:23 +0100 cnutwrote: > Hello Nikolaus, > Hello Andreas, > > > the good news: with the tutorial of Nikolaus, dmesg shows that the > device is alive... > [ 2895.846968] usb 1-4: new high-speed USB device number 4 using xhci_hcd > [ 2895.987845] usb 1-4: unable to get BOS descriptor > [ 2895.988919] usb 1-4: New USB device found, idVendor=0451, idProduct=d00e > [ 2895.988932] usb 1-4: New USB device strings: Mfr=33, Product=37, > SerialNumber=0 > [ 2895.988941] usb 1-4: Product: OMAP3630 > [ 2895.988949] usb 1-4: Manufacturer: Texas Instruments > [ 2898.990793] usb 1-4: USB disconnect, device number 4 > > > usb-starts-uboot shows only: > # ./usb-start-uboot.sh > Power on you gta04 with aux button pressed > Waiting for USB device vendorID=0x451 and productID=0xD009: > > It has to be run *before* powering on the gta04 to start uboot > dfu-util -l shows not a sign from the gta04 too (no "Found DFU ..."). > > > usb-flash-uboot-gta04.sh does not run too: > # ./usb-flash-uboot-gta04.sh nand uboot_files/ > and that will only work if the former script worked. Regards Andreas pgp6iUqAdrVwV.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hello Nikolaus, Hello Andreas, the good news: with the tutorial of Nikolaus, dmesg shows that the device is alive... [ 2895.846968] usb 1-4: new high-speed USB device number 4 using xhci_hcd [ 2895.987845] usb 1-4: unable to get BOS descriptor [ 2895.988919] usb 1-4: New USB device found, idVendor=0451, idProduct=d00e [ 2895.988932] usb 1-4: New USB device strings: Mfr=33, Product=37, SerialNumber=0 [ 2895.988941] usb 1-4: Product: OMAP3630 [ 2895.988949] usb 1-4: Manufacturer: Texas Instruments [ 2898.990793] usb 1-4: USB disconnect, device number 4 usb-starts-uboot shows only: # ./usb-start-uboot.sh Power on you gta04 with aux button pressed Waiting for USB device vendorID=0x451 and productID=0xD009: dfu-util -l shows not a sign from the gta04 too (no "Found DFU ..."). usb-flash-uboot-gta04.sh does not run too: # ./usb-flash-uboot-gta04.sh nand uboot_files/ 576+0 records in 576+0 records out 2359296 bytes (2.4 MB, 2.2 MiB) copied, 0.00659196 s, 358 MB/s 13+1 records in 13+1 records out 55524 bytes (56 kB, 54 KiB) copied, 0.000970685 s, 57.2 MB/s 13+1 records in 13+1 records out 55524 bytes (56 kB, 54 KiB) copied, 8.8559e-05 s, 627 MB/s 13+1 records in 13+1 records out 55524 bytes (56 kB, 54 KiB) copied, 9.6171e-05 s, 577 MB/s 13+1 records in 13+1 records out 55524 bytes (56 kB, 54 KiB) copied, 9.6118e-05 s, 578 MB/s 100+1 records in 100+1 records out 411048 bytes (411 kB, 401 KiB) copied, 0.00137635 s, 299 MB/s 3+1 records in 3+1 records out 14662 bytes (15 kB, 14 KiB) copied, 0.000305729 s, 48.0 MB/s 9+1 records in 9+1 records out 39304 bytes (39 kB, 38 KiB) copied, 0.000674798 s, 58.2 MB/s 60+1 records in 60+1 records out 247281 bytes (247 kB, 241 KiB) copied, 0.00115061 s, 215 MB/s dfu-util 0.9 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2016 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ dfu-util: Invalid DFU suffix signature dfu-util: A valid DFU suffix will be required in a future dfu-util release!!! dfu-util: No DFU capable USB device available Just to be sure: I have to start the gta04 for the above usage of dfu-util and usb-starts-uboot exactly the same way as for dmesg (plug usb cable, press and hold aux, insert battery)? @Nikolaus: > Do you by any chance know when you did last time flash the boot loader? S/N is 6131-0019. I started this thread, because I tried to flash the bootloader (begin of march 2018). Before, I never flashed the bootloader. Maybe it helps that QtMokov55 and QtMokov56 were running with the original bootloader. Maybe you know the bootloader version, because you assembled the device: The device was bought by 2013/01 as a complete device from pulster. Because there were issues with the hardware [1], it was sent to you for repairing. If you need more information, we should use private mail. > Maybe the u-boot environment of an old boot loader in NAND flash breaks > booting a new one and must be reset (which does not work if the device > does not boot). OK, seems to be the case here. Bootloaders before 2013/02 are only available at [2]. But there are no e. g. MLO files etc. in the directories. There are u-boot.bin, u-bootflash etc. and makesd. Do I have to flash using those makesd versions, which are in same directory than the u-boot files? Did the makesd syntax for creating a sd card change over the time? Let's say I have created a sd card with an old boot image and want to test it. > See: http://projects.goldelico.com/p/gta04-main/downloads/54/ In the document behind the link is written for "AUX pressed" with "NAND flashed and MMC installed": It does "MLO:MMC". I assume that is the case I need ot flash from sd card. Does it mean that I have to - remove usb cable and battery - put the sd card in the gta04 - press and hold aux button - insert battery - and release aux button when something from the sd was loaded (a menu, red screen etc.) Is the assumption correct? Regards cnut [1] http://lists.goldelico.com/pipermail/gta04-owner/2013-February/003924.html [2] http://download.goldelico.com/gta04-u-boot/ ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
On Sun, 11 Mar 2018 12:30:16 +0100 "H. Nikolaus Schaller"wrote: [...] > Yes, the RS232 serial console cable would be the easiest approach to look > what the device is doing/reporting. But if you don't have it, it does not > help. > > Do you by any chance know when you did last time flash the boot loader? > > There might be something incompatible with old and latest versions we don't > know yet. > > Maybe the u-boot environment of an old boot loader in NAND flash breaks > booting a new one and must be reset (which does not work if the device > does not boot). > > In that case you could try to reflash or completely boot the old boot loader > from an µSD where the old boot loader is stored on. > > We have an archive of all boot loader binaries and sources: > > http://download.goldelico.com/letux-u-boot/GTA04/ > > and > > http://download.goldelico.com/gta04-u-boot/ > > but without roughly knowing the version it is difficult to guess and write > instructions for preparing an µSD for that. > Well, the usb-nand flash script does reset the environment, so it should be a solution for such problems. I just need to build an easy to use package for that... So paving the way a bit. Regards, Andreas pgpxUZQtTcLKH.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hi, On Sun, 11 Mar 2018 11:32:22 +0100 cnutwrote: > Hello Andreas, > > > after ./usb-start-uboot.sh and dfu-util did not show any reaction, I > re-tried looking at dmesg - this time without success. > > I tried this on 2 different notebooks and a pc, each with two different > USB cables (one of the cables did work with a gta02): > 1) Remove battery, sim card, and sd card from the gta04 > 2) Press the aux button on the gta04. While holding the aux button plug > the gta to the usb port to the pc / notebook. I tried this with 5, 15 > and 30 seconds before releasing the aux button. Have you inserted the battery? Well, just in case. so, aux button, then usb plug, then battery? > 3) Looked ad the output of dmesg. > > I did not find anything like idVendor=0451, OMAP, Texas Instrurments. > > I charged the battery for ca. 2 hours in a gta02 to be sure that there > is enough power, and put the battery in the gta04. I still do not get > any reaction in dmesg or using dfu-util. > > The aux button itself ist at least pushable (I hear a small click). > > > A small thing that confuses me: > In the README file in spl-dfu-gta04a4.tar.gz is written, that for non > root users the "dfu-gta04.rules has to be copied into > /etc/udev/rules.d". There is no file dfu-gta04.rules. > Nishanth Menon wrote the readme, so I am not sure if this the right > mailing list to write about it. > Hmm. that is my readme. I have just forgotten to commit the rules file. Well, as said it is just needed for non-root usage. If no device pops up there, it cannot work anyway. Regards, An pgpvCbNiXCNtK.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hi cnut, sorry for not jumping into this earlier. Had too much to do with seasonal illness... > Am 11.03.2018 um 11:32 schrieb cnut: > > Hello Andreas, > > > after ./usb-start-uboot.sh and dfu-util did not show any reaction, I re-tried > looking at dmesg - this time without success. > > I tried this on 2 different notebooks and a pc, each with two different USB > cables (one of the cables did work with a gta02): > 1) Remove battery, sim card, and sd card from the gta04 > 2) Press the aux button on the gta04. While holding the aux button plug the > gta to the usb port to the pc / notebook. I tried this with 5, 15 and 30 > seconds before releasing the aux button. > 3) Looked ad the output of dmesg. I just tried this with a working GTA04: * remove battery * remove µSD card * plug in USB cable to an USB port of an ARM based SBC (OMAP5EVM but should not matter) * press AUX button * insert battery to trigger boot (although USB power is there, it is limited to 100mA which is not enough to start the OMAP) * look at dmesg of the host This is what I got: [ 151.391281] usb 1-2.1: new high-speed USB device number 5 using ehci-omap [ 151.542367] usb 1-2.1: unable to get BOS descriptor [ 151.548622] usb 1-2.1: New USB device found, idVendor=0451, idProduct=d00e [ 151.555925] usb 1-2.1: New USB device strings: Mfr=33, Product=37, SerialNumber=0 [ 151.563849] usb 1-2.1: Product: OMAP3630 [ 151.567959] usb 1-2.1: Manufacturer: Texas Instruments > I did not find anything like idVendor=0451, OMAP, Texas Instrurments. > > I charged the battery for ca. 2 hours in a gta02 to be sure that there is > enough power, and put the battery in the gta04. I still do not get any > reaction in dmesg or using dfu-util. > > The aux button itself ist at least pushable (I hear a small click). Without AUX button there is no USB report (except that my GTA04 boots from NAND). Also, inserting battery first (with or without AUX button) and then plugging the cable doesn't show a signal but boots from NAND (and then there is no USB activity). The reason is that the AUX button modifies the power-on boot sequence from NAND -> USB -> UART -> MMC to USB -> UART -> MMC -> NAND See: http://projects.goldelico.com/p/gta04-main/downloads/54/ Probably a wrong sequence of USB cable and battery insert makes the USB enumeration fail. > > > A small thing that confuses me: > In the README file in spl-dfu-gta04a4.tar.gz is written, that for non root > users the "dfu-gta04.rules has to be copied into /etc/udev/rules.d". There is > no file dfu-gta04.rules. > Nishanth Menon wrote the readme, so I am not sure if this the right mailing > list to write about it. > > > Any idea what how to proceed? > > > Regards > cnut > > > On 03/07/2018 07:53 PM, Andreas Kemnade wrote: >> On Wed, 7 Mar 2018 19:33:06 +0100 >> cnut wrote: >>> Thank you Andreas, for your detailed mail. >>> >>> > If you boot with aux pressed... >>> dmesg shows that the device is not dead. >>> >>> >>> > A serial cable would be helpful to find out. >>> If you are talking about a JTAG serial cable: I do not have one. But I >>> am interested in having a look how this works. If you have a link which >>> cable is needed and how to use it, I am happy to gain a little bit more >>> knowledge in this area. >>> >> Well, not a jtag cable, an ordinary serial rs232 console you use >> programs like minicom with. Yes, the RS232 serial console cable would be the easiest approach to look what the device is doing/reporting. But if you don't have it, it does not help. Do you by any chance know when you did last time flash the boot loader? There might be something incompatible with old and latest versions we don't know yet. Maybe the u-boot environment of an old boot loader in NAND flash breaks booting a new one and must be reset (which does not work if the device does not boot). In that case you could try to reflash or completely boot the old boot loader from an µSD where the old boot loader is stored on. We have an archive of all boot loader binaries and sources: http://download.goldelico.com/letux-u-boot/GTA04/ and http://download.goldelico.com/gta04-u-boot/ but without roughly knowing the version it is difficult to guess and write instructions for preparing an µSD for that. Ah, maybe the S/N of your device could help to find out the production date. >>> >>> > 1. clone my omap-utils fork... >>> > 2. do a make >> [...] >>> /bin/sh: 1: pkg-config: not found >>> src/pusb.c:45:20: fatal error: libusb.h: No such file or directory >>> #include >>> ^ >> apt-get install pkg-config >> Regards, >> Andreas BR, Nikolaus ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hello Andreas, after ./usb-start-uboot.sh and dfu-util did not show any reaction, I re-tried looking at dmesg - this time without success. I tried this on 2 different notebooks and a pc, each with two different USB cables (one of the cables did work with a gta02): 1) Remove battery, sim card, and sd card from the gta04 2) Press the aux button on the gta04. While holding the aux button plug the gta to the usb port to the pc / notebook. I tried this with 5, 15 and 30 seconds before releasing the aux button. 3) Looked ad the output of dmesg. I did not find anything like idVendor=0451, OMAP, Texas Instrurments. I charged the battery for ca. 2 hours in a gta02 to be sure that there is enough power, and put the battery in the gta04. I still do not get any reaction in dmesg or using dfu-util. The aux button itself ist at least pushable (I hear a small click). A small thing that confuses me: In the README file in spl-dfu-gta04a4.tar.gz is written, that for non root users the "dfu-gta04.rules has to be copied into /etc/udev/rules.d". There is no file dfu-gta04.rules. Nishanth Menon wrote the readme, so I am not sure if this the right mailing list to write about it. Any idea what how to proceed? Regards cnut On 03/07/2018 07:53 PM, Andreas Kemnade wrote: On Wed, 7 Mar 2018 19:33:06 +0100 cnutwrote: Thank you Andreas, for your detailed mail. > If you boot with aux pressed... dmesg shows that the device is not dead. > A serial cable would be helpful to find out. If you are talking about a JTAG serial cable: I do not have one. But I am interested in having a look how this works. If you have a link which cable is needed and how to use it, I am happy to gain a little bit more knowledge in this area. Well, not a jtag cable, an ordinary serial rs232 console you use programs like minicom with. > 1. clone my omap-utils fork... > 2. do a make [...] /bin/sh: 1: pkg-config: not found src/pusb.c:45:20: fatal error: libusb.h: No such file or directory #include ^ apt-get install pkg-config Regards, Andreas ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
On Wed, 7 Mar 2018 19:33:06 +0100 cnutwrote: > Thank you Andreas, for your detailed mail. > > > If you boot with aux pressed... > dmesg shows that the device is not dead. > > > > A serial cable would be helpful to find out. > If you are talking about a JTAG serial cable: I do not have one. But I > am interested in having a look how this works. If you have a link which > cable is needed and how to use it, I am happy to gain a little bit more > knowledge in this area. > Well, not a jtag cable, an ordinary serial rs232 console you use programs like minicom with. > > > 1. clone my omap-utils fork... > > 2. do a make [...] > /bin/sh: 1: pkg-config: not found > src/pusb.c:45:20: fatal error: libusb.h: No such file or directory > #include > ^ apt-get install pkg-config Regards, Andreas pgp79xZDVDXjS.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Thank you Andreas, for your detailed mail. > If you boot with aux pressed... dmesg shows that the device is not dead. > A serial cable would be helpful to find out. If you are talking about a JTAG serial cable: I do not have one. But I am interested in having a look how this works. If you have a link which cable is needed and how to use it, I am happy to gain a little bit more knowledge in this area. > 1. clone my omap-utils fork... > 2. do a make $ make Compiling: src/pserial.c Compiling: lib/serial_posix.c lib/serial_posix.c: In function ‘s_break’: lib/serial_posix.c:418:15: warning: unused variable ‘ret1’ [-Wunused-variable] int ret = 0, ret1; ^~~~ lib/serial_posix.c:435:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ Compiling: lib/file_posix.c Compiling: lib/f_status.c Compiling: lib/lcfg/lcfg_static.c Generating: pserial Compiling: src/ukermit.c Generating: ukermit Compiling: src/ucmd.c Generating: ucmd Compiling: src/gpsign.c Generating: gpsign Compiling: src/tagger.c src/tagger.c: In function ‘generate_tag’: src/tagger.c:191:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] return (u32) param - (u32) buffer; ^ src/tagger.c:191:23: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast] return (u32) param - (u32) buffer; ^ Generating: tagger Compiling: src/sysrq.c Generating: sysrq Compiling: src/pusb.c /bin/sh: 1: pkg-config: not found src/pusb.c:45:20: fatal error: libusb.h: No such file or directory #include ^ compilation terminated. makefile:195: recipe for target 'src/pusb.o' failed make: *** [src/pusb.o] Error 1 What went wrong? I use Debian Stretch. build-essential and libusb-1.0-0-dev are installed. Regards cnut On 03/04/2018 12:15 AM, Andreas Kemnade wrote: 1. clone my omap-utils fork: https://github.com/akemnade/omap-u-boot-utils 2. do a make and sudo make install there (will need libusb-1.0-0-dev) ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner
Re: [Gta04-owner] Trying to flash U-Boot led to a bricked device
Hi, first measure, take a deep breath, I do not believe your device is dead. If you boot with aux pressed (*before* powering on the device) and have it connected to the computer, do you still see lines like that in kern.log or dmesg: usb 1-2.4: New USB device found, idVendor=0451, idProduct=d00e usb 1-2.4: New USB device strings: Mfr=33, Product=37, SerialNumber=0 usb 1-2.4: Product: OMAP3630 usb 1-2.4: Manufacturer: Texas Instruments You have still good chances to do something. On Sat, 3 Mar 2018 22:09:28 +0100 cnutwrote: > Hello, > > > I tried to flash U-Boot and now my gta04 does not react any more. If > anybody has an idea how to unbrick the device or can tell me what I did > wrong, please let me know. > > Here is a description of what I did: > Using "makesd gta04 debian", I wrote data on a sd card. The sd card was > put into the gta04. After reading in this post [1] how to flash U-Boot, > and after several attemps [2] the red flashing screen appeared. The red > color flashed only for some seconds. After that the gta04 screen showed > a picture which looked like a tv showing a dead channel. The dead > channel picture did not go away for some time, so I powered off the > gta04 by pressing the power button for some seconds. > Well, a serial boot log would be interesting. Somehow the upgrade process is done half. > Now I am not able to power on the device. I tried various combinations > of pressing the aux and power button, with and without an sd card (with > a 4 year old working qtmoko) in the device. > The battery is not empty. I use a gta04a4. > So inserting the freshly-generated sd card for a second time does not help? So we have at least two possibilities: 1) sd card contact problems 2) uboot environment is trashed. A serial cable would be helpful to find out. Or simply try another sd card. If that fails and the above usb messages are appearing: 1. clone my omap-utils fork: https://github.com/akemnade/omap-u-boot-utils 2. do a make and sudo make install there (will need libusb-1.0-0-dev) 3. sudo apt-get install dfu-util 4. wget https://misc.andi.de1.cc/spl-dfu-gta04a4.tar.gz 5. tar -zxvf spl-dfu-gta04a4.tar.gz 6. cd spl-dfu 7. sudo ./usb-start-uboot.sh 8. remove battery from your gta04. 9. attach it with usb. 10. press and hold aux button 11. insert battery 12. tell me what happend Expected: u-boot is successfully started and waits for usb input lcd stays black But you should see in sudo dfu-util -l dfu-util 0.9 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2016 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Found DFU: [0451:d022] ver=0215, devnum=95, cfg=1, intf=0, path="1-2", alt=4, name="bootscript", serial="UNKNOWN" Found DFU: [0451:d022] ver=0215, devnum=95, cfg=1, intf=0, path="1-2", alt=3, name="script", serial="UNKNOWN" Found DFU: [0451:d022] ver=0215, devnum=95, cfg=1, intf=0, path="1-2", alt=2, name="rd", serial="UNKNOWN" Found DFU: [0451:d022] ver=0215, devnum=95, cfg=1, intf=0, path="1-2", alt=1, name="fdt", serial="UNKNOWN" Found DFU: [0451:d022] ver=0215, devnum=95, cfg=1, intf=0, path="1-2", alt=0, name="kernel", serial="UNKNOWN" If that works, your gta04 should also be charging (if your cable is not too weak Then there is the script called usb-flash-uboot-gta04.sh in that directory which can write a fresh uboot into your nand flash. Usage: ./usb-flash-uboot-gta04.sh nand /path/to/uboot-files /path/to/uboot-files should contain MLO, u-boot.img, boot.scr, splash.rgb16z, menu.rgb16z you can get them e.g. from here: http://download.goldelico.com/letux-u-boot/GTA04/latest Regards, Andreas PS: the source of that spl-dfu stuff is commit b76421c9f6577f0498a02512bf9aed8e31c9527c of the gta04 uboot (http://projects.goldelico.com/p/gta04-uboot/source/tree/master/) pgpk_ZXqJ7ubI.pgp Description: OpenPGP digital signature ___ Gta04-owner mailing list Gta04-owner@goldelico.com http://lists.goldelico.com/mailman/listinfo.cgi/gta04-owner