Re: [U-Boot] U-book and GPLv3? (fwd)
Robin Getz sez, > Assuming that the _licensed_ amateur could modify the phone enough > that it _could_ operate on frequencies allocated for amateur use. > The only thing that would be potentially close is a European GSM phone: > Rx Tx > E-GSM-900 880.0–915.0 925.0–960.0 MHz > R-GSM-900 876.0–915.0 921.0–960.0 MHz > T-GSM-900 870.4–876.0 915.4–921.0 MHz > & the US amateur band at 902 - 928 MHz. That would be the US ISM band. > I don't think any of the CDMA phones are close enough to the amateur bands to > have a hope of working - but I'm not as familiar with CDMA as GSM. Since I actually do wireless work I'll make another comment. There are research and development exemptions to the licensing requirements. Ergo I can build, test or modify any radio I want for research purposes no license required. What I can't do is deploy or sell them. Even with licensed devices changes to the hardware or firmware are allowed as long an an engineer believes that the changes will not have any effect on the radio's meeting the applicable standards. Also for radios operating on the cellular band there are really two licenses. One is the regulatory license. The other is the carriers certification. Matt Harper Tehama Wireless ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-book and GPLv3? (fwd)
Robin Getz sez, > This is in no way trying to interperate the GPL3 for others (that is for > lawyers to do) - but just a question from an interested developer - to me - > it seems like tivo all over again. All Tivo needs to do is just make the > network a piece of their application - and they have an out... I have an example using gambling machines. Say I have a friend Don Drakulich who runs a small peep show empire and has bought a five hundred slot machines from a defunct Los Vegas Casino. Don Drakulich thinks of himself as and honest businessman, meaning he has free and clear title to these machines having bought them at an auction. And why he plans on repurposing them as adult video peep show consoles. They're perfect being based on slightly modified open source dev board running Linux. But however they have 'secure boot' so he can't modify the software so that they can legally be used in his peep show booths. But then again because his software developer has contacts with a board assembly house, he is able to get the secure boot processors replaced at a mere cost of $20 per unit or $10,000 for the lot. No big deal. So it sounds to me that secure boot has merely annoyed honset guys like Don. And not even slowed down the Serbian Mafia because they have a couple of their software guys working for a slot machine manufacturer. But you're made it hard for someone who casually comes into possession of a slot machine to re-purpose it as say a video jukebox. Also if anyone is still reading at this point I'll say this having worked on industrial controls that can both kill people or cause expensive damage to machines, equipment and product. The general trend is that the safety monitoring system must be separate from the command and control system. IE, the PLC can try to turn on the $100,000 vacuum pump when the oil level is too low, but the safety interlock won't let the pump turn on. That's the world I come out of and it's why I find all of the GPL-V3 will negative impact product safety arguements lacking. And why I can assure you that none of the people involved in those industries care about the GPL. And I'll say this, if you are primarily relying on a piece of software to prevent injury or death you really need to rethink what you are doing. For a good example of what can happen one can view this US Chemical Safety Board report on a accident that occurred at at facility involving controls that I personally worked on. http://www.chemsafety.gov/investigations/detail.aspx?SID=30 Matt Harper. Tehama Wireless. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] use of C99
Premi, Sanjeev sez, > I was referring to declaring variable within #ifdefs with > belief that > use will be contained. > > e.g. > #ifdef CONFIG_COOL_FEATURE > int i; > int* ptr ; > ... > ... > #endif > > ... > ... 2 screenful down; in same function... > ... > > #ifdef CONFIG_HOT_FEATURE > u32 i; > void* ptr; > ... > ... > #endif > > Maybe for sometime the usage seems contained. Until someone > decides to have both the COOL and HOT feature. Pops out of hole, looks at shadow, 6 more weeks till we ship... Um... my feeling is that if one is going to declare a variable inside a #ifdef then that variable ought to be called something like int indx_CONFIG_COOL_FEATURE and u32 indx_CONFIG_HOT_FEATURE Matt Harper Tehama Wireless ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot environment variable storage
twebb sez, > Does u-boot have support for storage of environment variables in > file form? For example, in a file on a FAT32 file system > residing on a MMC card? The only reason I can think you'd want to do that is to be able to set environment variables in linux user land. But then I have a small brain. If you do, take a look at fw_printenv under \tools\something_or_other Matt Harper --- ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Cloning, Maybe silly question
I have a suggestion/question. Would it be easy, hard, silly to add a CLONE command to the make file? (Are a separate make script?) So if someone wants to create a new board based on an existing board they could just type, make CLONE at91sam6263ek_CONFIG myboard or if it's script ./clone.sh at91sam6263ek_CONFIG myboard The make file would clone the at91sam9263ek board configuration and put it in a new directory called myboard and update the makefile? Matt Harper Tehama Wireless. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot for ARM
Amandeep Bhullar sez, > I have an Atmel AT91SAM9263 evaluation board with an > arm926ejs based processor. I want to configure U-boot > for this and want to have a USB device boot option > available too. Though the U-boot will be in NAND > Flash but i want the board to boot from a USB device > like a USB Flash drive etc. Sounds like an adventure! > I was reading the README and it talks about configuring a > large number of options. Where do I define these options? > In which file? For your board the file with many of the defines is. include\configs\at91sam9263ek.h > if i just give the command > $ make arm926ejs_config > if comes with a message > make: *** No rule to make target > 'arm926ejs_config'. Stop. You need to type, make at91sam9263ek_config make Also it's a good idea to have the environment variable CROSS_COMPILE Set to point to your tool chain, as in CROSS_COMPILE=\opt\mytoolchaintool\arm-elf- where the directory \opt\mytoolchaintool\ Contains your tools, such as arm-elf-gcc etc etc. > Can anybody help me in how to obtain a .bin file for my > processor that i can load in NANDFlash and use this U-boot. Can't help there, don't know if it's possible. I do know that you can boot out of NOR (parallel) and Atmel Dataflash (Serial). I would suggest building the standard u-boot and learn how it works and then go from there. Mr Foo --- ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 2/5] ARM: Add/Improve support for Atmel AT91RM9200DK/E
I checked out the latest snapshot of the AT91 branch and was able to build, a working version of u-boot. The Flash CFI support works in that I was able to write both the AT91RM9200EK's flash, and the AT49BV642D flash on my board. The snapshot I used was this one. http://git.denx.de/?p=u-boot/u-boot-at91.git;a=commit;h=df362482d656c1e17221845ab628467bbd9d0ef7 However few points. The board comes from the factory with a boot loader (BOOT.BIN) that decompresses and u-boot from address 1001 and then executes it. In order for this to work you need to define #define CONFIG_SKIP_LOWLEVEL_INIT to disable the low level init since it has already been done BY BOOT.BIN, and the boot loader is running out of ram, SO doing it again will result in a hang. Note as well to builD the code I had to follow the these instructions. > mkdir at91rm9200ek > make O=at91rm9200ek at91rm9200ek_config > make O=at91rm9200ek This puts all the object files in the output directory at91rm9200ek. Otherwise I got a error complaining that make couldn't find /include/tools/mach-types.h This probably only applies to this branch, not the main. Anyways, thanks bunches to Ulf and Jean-Christophe. PS: You can download an u-boot via xmodem through the debug port. However this version of u-boot is too big to download via this way (limit seems to be 128k. In order to get the binary small enough I had to remove USB support. Matt Harper Tehama Wireless. --- Oppressing electrons since 1908 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 2/5] ARM: Add/Improve support for Atmel AT91RM9200DK/E
Ulf! Here I was getting ready to try and add support for the AT91RM9200EK and I see your patches. I have a question? Does the new AT91RM9200EK support CFI? Is so no problem for me, otherwise I got that working on last week for my board based on the AT91RM9200EK (with AT49BV642D flash). The changes to the at91rm9200ek.h were trivial, however I had to disable buffered writes as the AT91BV642D didn't support it as the '642 lies about supporting buffered writes. I suspect that the AT49BV6414 used on the ek, may have the same issue as when I was fixing the kernel to support the '642 there was an identical patch for the 6414 + plus the data sheet doesn't mention it in the summary. Matt Harper Tehama Wireless ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] My Linux kernel hangs at the Uncompressing Linux ... phase
Diptopal Basu, > I have compiled a Linux kernel ( version 2.6.22.19 ) for > ARM at91rm9200dk board, I used the mkimage utility in U < boot load the kernel at a specific area of memory . > ( Skyeye Simulator ) > > However I get the Uncompressing Linux ... message and it > stays at that line indefinitely ... attaching screenshot > ... this is on the skyeye simulator . That is a fundamental issue with the build of the kernel itself. IE, something fundamentally wrong with the image. u-boot uncompressed it, then jumped to it, and it crashed hard. > I am just booting the kernel I do not have a device tree > blob or anything else here , that is , I compiled the > kernel with at91rm9200dk defconfig, got the zImage , Woah back up. zImage? I'm not sure what the difference is but I use the uImage to boot the kernel. > used mkimage to add a U boot header and > using bootm command to start it . > What could be the problem ? Probably the setup of mkImage is wrong, kernal being loaded in the wrong place in memory, etc or the machine type being passed to the kernel is wrong? PS: I can send you a known working uImage and zImage for the AT91RM9200EK that you can try. Just maybe not today as it's Christmas. Matt ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Problem building fw_printenv un u-boot 1.3.4
Dear Wolfgang, > In message pink sez, >> So still doing some hacking trying to build this and >> wondering if either u-boot-1.3.4 is busted, or the >> instructions are wrong. > > v1.3.4 is old. Why don't you use current code? Far as I can tell v1.3.4 is from Sept this year. Is it older than that? >> Note sure it it works or not. When I run it I get the >> following error. > > > > Cannot parse config file: No such file or directory > > Obviously you have to create a config file in your target > file system... I'm sorry I should have done a little more poking about before I posted that. I put fw_env.config in /etc and changed the entry to and at least /dev/mtd1 0xe000 0x2000 0x2000 #/dev/mtd1 0xe000 0x2000 0x2000 Then created device nodes. mknod /dev/mtd0 c 90 0 mknod /dev/mtd1 c 90 1 After that fw_printenv works. However fw_setenv returns an error. # ./fw_setenv beets are_good Can't open /dev/mtd1: Permission denied Error: can't write fw_env to flash It's probably something stupid on my part. But at least I got this far. Would using the latest tree be better? It appears at least that make at91rm9200dk_config make env doesn't work because fw_printenv needs some kernel headers to build correctly. Mr Foo ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Problem building fw_printenv un u-boot 1.3.4
So still doing some hacking trying to build this and wondering if either u-boot-1.3.4 is busted, or the instructions are wrong. Poking about it looks like fw_printenv needs some kernel headers in order to build correctly. Specifically I believe it needs include/mtd/mtd-user.h On my system I was able to build it manually using armv4l-uclibc-gcc -Wall -DUSE_HOSTCC -I/home/tu/workspaces/AccessPoint/Kernel/include/ -I/home/tu/workspaces/uboot/u-boot-1.3.4/tools crc32.c fw_env.c fw_env_main.c -o fw_printenv Where /home/tu/workspaces/AccessPoint/Kernel/include/ is the location of my embedded kernels header files. Note sure it it works or not. When I run it I get the following error. Cannot parse config file: No such file or directory Mr Foo ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Problem building fw_printenv un u-boot 1.3.4
Hi, I'm back haxing at u-boot. Specifically I'm trying to build fw_printenv so that I can use u-boots environment to store my boards MAC address. I've been able to build a u-boot that runs off of u-boot-1.3.4 for the AT91RM9200DK. However when I try and build the utilities to read and write the env I get the following error below. Any ideas why this is happening? Matt Tehama Wireless --- # make env CROSS_COMPILE=armv4l-uclibc- MTD_VERSION=old make -C tools/env all MTD_VERSION=old || exit 1 make[1]: Entering directory `/home/tu/workspaces/uboot/u-boot-1.3.4/tools/env' armv4l-uclibc-gcc -Wall -DUSE_HOSTCC -I/home/tu/workspaces/uboot/u-boot-1.3.4/include -DMTD_OLD crc32.c fw_env.c fw_env_main.c -o fw_printenv In file included from /home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd.h:12, from fw_env.c:36: /home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:11: error: expected specifier-qualifier-list before ‘uint32_t’ /home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:16: error: expected specifier-qualifier-list before ‘uint32_t’ /home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:61: error: expected specifier-qualifier-list before ‘uint8_t’ /home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:72: error: expected specifier-qualifier-list before ‘uint32_t’ /home/tu/workspaces/uboot/u-boot-1.3.4/include/linux/mtd/mtd-abi.h:93: error: expected specifier-qualifier-list before ‘uint32_t’ fw_env.c: In function ‘fw_setenv’: fw_env.c:386: error: ‘uint8_t’ undeclared (first use in this function) fw_env.c:386: error: (Each undeclared identifier is reported only once fw_env.c:386: error: for each function it appears in.) fw_env.c:386: error: expected expression before ‘)’ token fw_env.c:386: error: too few arguments to function ‘crc32’ fw_env.c: In function ‘flash_io’: fw_env.c:400: error: ‘erase_info_t’ undeclared (first use in this function) fw_env.c:400: error: expected ‘;’ before ‘erase’ fw_env.c:431: error: ‘erase’ undeclared (first use in this function) fw_env.c: In function ‘env_init’: fw_env.c:621: error: ‘uint8_t’ undeclared (first use in this function) fw_env.c:621: error: expected expression before ‘)’ token fw_env.c:621: error: too few arguments to function ‘crc32’ fw_env.c:645: error: expected expression before ‘)’ token fw_env.c:645: error: too few arguments to function ‘crc32’ make[1]: *** [fw_printenv] Error 1 make[1]: Leaving directory `/home/tu/workspaces/uboot/u-boot-1.3.4/tools/env' make: *** [env] Error 1 # ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] at91rm9200: fix broken boot from nor flash
Wolkgang Denk sez, > Jens Scharsig claims, >> I think my patch only don't work on AT91RM9200DK, >> AT91RM9200EK or AT91RM9200DF board. Blame it on this >> solution is the #ifdef construct in /cpu/arm920t/start.s >> at line 264. There are no low_level_init run for DK, >> EK andDF board. > I agree. That code looks pretty bogus to me, too. I've had the problem where trying to run u-boot directly from rom fails, and read various bits about the defines in start.s being goofed. > I can confirm that removing the "defined(CONFIG_AT91RM9200DK) ||" > part there makes the code work on the AT91RM9200DK board (j24: > patch following ASAP). > > Any AT91RM9200EK and AT91RM9200DF users out there to test > this? I'll be happy to do that, I have an AT91RM9200-EK board that I'm doing dev on right now. I assume that I can download the current tree and get the patched version? Matt --- Beating my head against the AT91RM9200 for too long. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] AT91RM9200 boots from NOR Flash or not
Martin Hejnfelt sez, > Message from Jens Scharsig, >> I am a little bit confused. We have designed a new AT91RM9200 >> based board. It should boot from 16-bit NOR Flash. I have read >> many relevant article in the forum, but I don't know , which >> board should I use as a base. I have look at the actual source >> (2008.10 and> git), and I think, u-boot can't boot without a >> preloader as long> CONFIG_AT91RM9200 is defined. Is there an >> open patch to resolve this? Can you get an example for a working >> implementation? I built u-boot 1.3.4 for the AT91RM9200DK and was able to hack in support for the flash chip I'm using. You might try the same. The setup I'm using is to store boot.bin from atmel in flash at . And a copy of u-boot.gz at 1001. The way I did was to enable the AT91RM9200's boot serial port boot loader and download Atmels loader.bin via XMODEM. Then download uboot.bin via XMODEM. Once that it downloaded you should get a prompt. For auto booting I have Atmels boot program boot.bin stored in flash at 1000-10005fff. And gzipped u-boot stored at 1001-1001. > It's true that it won't boot when CONFIG_AT91RM9200 > is defined. I don't know why it is like this since older > versions of U-boot didn't have this problem (it changed > around 1.3.0 if I remember correctly). Hmmm... > It's almost like even if you do not define CONFIG_SKIP_LOWLEVEL_INIT > and/or CONFIG_SKIP_RELOCATE_UBOOT, it still works like they were. > Maybe it's because Atmel usually supplies their own Boot.bin > along with the Development Kit (the configuration I would say > you should use as example for your own) You can resolve this by > editing two lines in the start.S file of the ARM920T cpu specific > directory. In version 2008.10 its line 181 you can delete this, or > change to ifdef, and again in line 264 you can either delete the if > statement, or just make it branch to the lowlevel_init no matter > what. > > I know its what someone would call a hack, but it works :) This is the second place I've seen this. I've been using atmels boot.bin loader to uncompress u-boot and it seems to work okay. Matt Harper Tehama-Wireless. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Building u-boot for the AT91RM9200-EK circa 2008
Wolfgang Denk <[EMAIL PROTECTED]> wrote: > The thing is: we will not accept any such (new) code for > mainline. And switching to using the CFI driver is trivial. Okay then. I was able to compile u-boot 1.3.4 for the AT91RM9200DK with changes so that it can handle writing to the flash on my custom board base don the AT91RM9200EK. Seems to work but writes to flash are very slow... However it's a hack of the DK board. I will try over the next week or two to make a version of the AT91RM9200DK u-boot that uses the CFI driver. And then submit a patch for that. Matt Harper Tehama Wireless ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Building u-boot for the AT91RM9200-EK circa 2008
Wolfgang Denk sez, > The thing is: we will not accept any such (new) code for > mainline. And switching to using the CFI driver is trivial. Okay so what I've learned. 1)You can build the AT91RM9200DK version of u-boot with u-boot-1.3.4 and it works. At least I got a prompt. So one can use the AT91RM9200DK as a starting point for the AT91RM9200EK. 2) At this point I think relying on any older patched version of u-boot that supports the AT91RM9200EK is probably not workable and not worth doing. 3) Anyone starting a project based on the AT91RM9200EK is making big mistake because the AT91RM9200 chip has been abandoned by its mother. At least I have I have some sort of peg in the ground to start with. Right now I worry about trying to get the CFI to work because as a noob I'm in the dark on a lot of things 1) How to port the CFI to the AT91RM9200DK. 2) Create a board support for the AT91RM9200EK based on that. 3) Generate patches that are acceptable. Personally I think that Atmel is doing people a disservice by not classifying the AT91RM9200 as not for new designs since there is no current support for it. Matthew Harper. Tehama Wireless. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Building u-boot for the AT91RM9200-EK circa 2008
Jean-Christophe sez, > > make distclean > > make at91sam9263ek_config Sorry bad paste job that should be make at91rm9200ek_config. > > make > CROSS_COMPILE= > why do you try to use the at91sam9263ek board on the > AT91RM9200EK? > > and the AT91RM9200EK is not so far from the AT91SAM9200DK > which is mainline and they are not so much different execept > some PIO settings I could try that and see it it will work. Would be nice to have some sort of peg in the ground what I can build something that works. > IIRC Ulf send some patch 2 years ago > > Maybe he can resend a rebased version? Would have been nice if they'd included it considering that the AT91rm9200-ek is an odd ball with no real long term future. I'll try the AT91RM9200DK and see if I can get anything out of that. I worry that with the old source I can't get a working tool chain for it. How hard would it be to have a standard Hello World program build on u-boot that just does a bare init of the hardware and spits "Oh Hai" out the serial port? At least then you can verify that the tool chain and startup code is mostly working. Hmmm... Matthew Harper Tehama Wireless. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Building u-boot for the AT91RM9200-EK circa 2008
Hi, first post here. vis: Building u-boot for the AT91RM9200-EK circa 2008 Is this still possible all things considered? It appears that this board is left behind in a backwater sometime around 2006. Problem is I need to compile a new version of u-boot for my new board based on the AT91RM9200 and I'm having a lot of trouble. My board is very closely based on the AT91RM9200-EK, pretty much the same except the flash has changed. So I need to modify u-boot to handle the new flash (AT49BV642D). I'm running into real problems, at least for a noob. On my board I can get two versions of u-boot to run, the 1.1.5 version that comes with the AT91RM9200 development kit. And an ancient u-boot 1.1.1 that I got off Atmel's website which surprisingly enough will write to the new flash chip I have installed, even though it thinks there is only 2M installed instead of 8M And I can use it to do setenv, etc and load uboot 1.1.5 into flash and boot linux over the network connection. So far so good. So my hardware works, I just need a version of u-boot that supports the AT49BV642D. Patching the source seems easy enough. However. Problem is that the official distribution of u-boot has no support for the AT91RM9200-EK. Which is sad. Very very sad. I tried compiling u-boot from scratch using the instructions on this page. http://www.linux4sam.org/twiki/bin/view ... _x_sources Namely, wget ftp://ftp.denx.de/pub/u-boot/u-boot-1.1.5.tar.bz2 tar xvjf u-boot-1.1.5.tar.bz2 cd u-boot-1.1.5 wget ftp://www.linux4sam.org/pub/uboot/u-boo ... 5.diff.bz2 bzcat u-boot-1.1.5_atmel_1.5.diff.bz2 | patch -p1 Then I fixed up two lines in the examples make file adding an .o at the end in order to make the 3.81 linker happy. Line 147 : $(obj)%.srec: $(obj)%.o Line 150 $(obj)%.bin: $(obj)%.o Then make distclean make at91sam9263ek_config make CROSS_COMPILE= Where my compiler is gcc version 3.4.3 (release) (CodeSourcery ARM Q1B 2005) I've also tried gcc version 4.1.1 (CodeSourcery ARM Sourcery G++ 2006q3-26) and gcc 4.1.1 from timesys. In each case I get a built version of u-boot.bin. However when I download it the same way I use the other two wokring binaries of u-boot that I have it just hangs with no output. I've also tried gzipping it and trying to have boot.bin load it from flash, but it hangs as well. I also tried compiling with an old version of gcc 3.4.1 but it wouldn't compile the source due to a compiler bug/issue. Google indicates the error is due to the compiler assuming a hard fpu. Anyone have advice on how to proceed from here? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
