Hello António,
Awesome to hear everything is working for you. Thanks as well for updating us on your solution - that's helpful for us and any future folks who run into something similar. Feel free to create a new thread if yall have questions in…
YiFong Lin said: 1. source environment-setup
2. arm-oe-linux-gnueabi-gcc $CFLAGS helloworld.c -o helloworld
or
3. $CC helloworld.c -o helloworld -mfpu=neon -mfloat-abi=hard
For reference, the best/cleanest way is probably a combination of both approaches…
Hi Sean,
Sean Wei said: I had installed RT-linux patch, but the interrutp latency still exist,
I am not sure what the RT linux patch is, but the Processor SDK Linux provides a RT Linux package. Please try to use it if possible.
After talked to our sw dev…
Part Number: AM3358 Hi,
My LCD has a RGB 666 interface. So to interface it to the MCU, I use most significant 6 bits of each color from the MCU (MCU Blue2-Blue7 to LCD Blue 0-Blue 5). Is my understanding correct?
Also the Table 13-7 only says upto 16…
Part Number: AM3358 I'm occasionally seeing sluggish behavior due to a musb irq:
I've read in other forums that enabling CONFIG_USB_TI_CPPI41_DMA and disabling CONFIG_MUSB_PIO_ONLY may fix this issue, but h ow can I be sure that I won't be affected…
Hello,
Sorry for the confusion. I understand your original question is about the compiler.
user6544278 said: - could the compiler version really be responsible for this behaviour?
- if yes, what change in compiler v20 could have fixed this?
As I mentioned…
Part Number: AM3358 hi:
I am trying to use use 335x GPMC to access nor flash , printf: physmap-flash physmap-flash.0: can't request region for resource [mem 0x10000000-0x13ffffff]。 What is the error ?
Thanks,
root@am335x-evm:~# insmod physmap.ko […
Hello Michael,
Thank you for the inputs.
Regarding the complier question - i would suggest starting a new thread quoting the complier version and asking your query.
Regards,
Sreenivasa
Part Number: AM3358 Other Parts Discussed in Thread: UNIFLASH , Hello,
I am working on an issue where our released image is being corrupted before it leaves our factory. I have managed to identify the issues as being an orphaned inodes in a few directories…
Hi Hongtai,
If the issue is still open, can you please check the following thread if it is helpful?
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1332523/beagl-bone-black-problems-reading-from-emmc-boot-partitions-on-beaglebone…