Welcome, Guest

Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
MSP430 / programming msp430F167 microcontroller
« Last post by Priyanka Deshmukh on December 05, 2018, 03:42:47 PM »
Hello,
I have recently switched to CCS 8.2.0 for programming.
I use Olimex  MSP430-JTAG-TINY-V2 to burn my hex file to the microcontroller. However, when i switched to new IDE, the program is same without any changes and compiled my program correctly and have a ihex file now.
Can i burn this file using MSP430-JTAG-TINY-V2 to my microcontroller? Will it give an error? Already tried the program doesnot work. Is this because it is not compatible with CCS new versions? How to proceed?
22
TERES DIY Laptop / Re: Max resolution supported via eDP?
« Last post by nearsky on December 04, 2018, 05:32:52 PM »
The AOSC distro appears to work out the box with 1080p. For the Teres you have the option of a base or MATE install, either to a SD card or eMMC.
23
A13 / A13 Mainline U-boot "Please RESET the board" problem
« Last post by satilla on December 03, 2018, 05:04:12 PM »
I have compiled mainline u-boot according to wiki page. These are rules which I followed;



Code: [Select]
# mkdir a13-olinuxino-kernel_3.4.90
# cd a13-olinuxino-kernel_3.4.90

2.2. Building mainline u-boot

Then let’s download the uboot sources from GitHub repository
Note that the u-boot for A13-OLinuXino is tested with the next branch:

# git rev-parse --verify HEAD
1733259d25015c28c47990ec11af99b3f62f811c

Download u-boot sourses:
# git clone git://git.denx.de/u-boot.git
After the download you should have a new directory

#cd u-boot

Load the configuration file for A13-OLinuXino.

#make CROSS_COMPILE=arm-linux-gnueabihf- A13-OLinuXino_defconfig

you can configure some u-boot settings like DDR3 settings, clocks and other with:

#make menuconfig

It is recommended to choose:
 
[*]Enable workaround for booting old kernels

the board has stable behaviour with
[408] sunxi dram clock speed
[204] sunxi mbus clock speed

but you can choose other settings depending from your application

save it the settings and exit

build the u-boot

#make CROSS_COMPILE=arm-linux-gnueabihf-

When the build has completed, there will be u-boot-sunxi-with-spl.bin available in your u-boot tree.

Now you have to create a new boot.cmd file with the following contain

setenv bootm_boot_mode sec
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait panic=10
load mmc 0:1 0x43000000 script.bin || load mmc 0:1 0x43000000 boot/script.bin
load mmc 0:1 0x42000000 uImage || load mmc 0:1 0x42000000 boot/uImage
bootm 0x42000000

convert boot.cmd in boot.scr with the next command

# mkimage -C none -A arm -T script -d boot.cmd boot.scr
 
The result should be a new boot.scr file that you have to copy to the first SD card partitition(where uImage and script.bin file are located)


4. Format and setup the SD-card
--------------------------------
We suggest 4GB class 10 micro sd-card but you can use any card between 2GB and 16GB.

First we have to make the correct card partitions, this is done with fdisk.

Plug SD card into your SD card reader and enter in the terminal

# ls /dev/sd
Then press two times <TAB> you will see a list of your sd devices like sda sdb sdc note that some of these devices may be your hard disk so make sure you know which one is your sd card before you proceed as you can damage your HDD if you choose the wrong sd-device. You can do this by unplugging your sd card reader and identify which “sd” devices remove from the list.

Once you know which device is your sdcard like sda use this text instead of the sdX name in the references below:

# fdisk /dev/sdX
then do these steps:

4.1. p
will list your partitions

if there are already partitions on your card do:

4.2. d enter 1
if you have more than one partitition press d while delete them all

4.3. create the first partition, starting from 2048
n enter p enter 1 enter enter +16M

4.4. create second partition
n enter p enter 2 enter enter enter

then list the created partitions:
p enter
if you did everything correctly on 4GB card you should see something like:

Disk /dev/sdg: 3980 MB, 3980394496 bytes
123 heads, 62 sectors/track, 1019 cylinders, total 7774208 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1            2048       34815       16384   83  Linux
/dev/sdg2           34816     7774207     3869696   83  Linux

4.7. w

write changes to sd card
now we have to format the file system on the card:

the first partition should be vfat as this is FS which the Allwinner bootloader understands

# mkfs.vfat /dev/sdX1
the second should be normal Linux EXT3 FS

# mkfs.ext3 /dev/sdX2

5. Write the Uboot and sunxi-spl.bin
-------------------------------------
You should be in /home/user/a13-olinuxino-kernel_3.4.90# directory
Note that you have to write u-boot-sunxi-with-spl.bin in /dev/sdX (not sdX1 or sdX2)

# dd if=u-boot-sunxi/u-boot-sunxi-with-spl.bin of=/dev/sdX bs=1024 seek=8

Note that if you use mainline u-boot then you have to copy the generated boot.scr file in the first sdcard partition. For example:

# mkdir /mnt/sd
# mount /dev/sdX1 /mnt/sd
# cp /u-boot/boot.scr /mnt/sd/


7. Write script.bin file
-------------------------
script.bin is a file with very important configuration parameters like port GPIO assignments, DDR memory parameters, Video resolution etc,
download the script.bin using wget command
# wget https://github.com/OLIMEX/OLINUXINO/raw/master/SOFTWARE/A13/A13-build/script.bin
# cp script.bin /mnt/sd
# sync
# umount /dev/sdX1


I have copied boot sector (0 to 2047) from olimex A13 image to new sd card and it starts u-boot without error. I think there is a problem with my u-boot compiling or config file...
I just want to use u-boot command prompt. What am I missing?
24
JTAG / Re: ARM-USB-OCD-H Mac FTDI drivers
« Last post by julesb on December 03, 2018, 04:10:50 AM »
Should we request FTDI to add PID=43/VID=5562 for the ARM-USB-OCD-H? Other Mac users must also have this problem in the field.

Also, I second this request. Olimex should request FTDI add this PID/VID to their drivers, particularly for OS X.
25
JTAG / Re: ARM-USB-OCD-H Mac FTDI drivers
« Last post by julesb on December 01, 2018, 05:54:30 AM »
I'm pleased to say I did get this working in the end. However it's not ideal to be running with the system integrity protection disabled. The sooner this is fixed the better.
26
JTAG / Re: ARM-USB-OCD-H Mac FTDI drivers
« Last post by julesb on December 01, 2018, 05:33:16 AM »
Actually, to answer my own question I was able to get around this using the very dubious method of disabling the system integrity protection feature:

https://developer.apple.com/library/archive/documentation/Security/Conceptual/System_Integrity_Protection_Guide/ConfiguringSystemIntegrityProtection/ConfiguringSystemIntegrityProtection.html#//apple_ref/doc/uid/TP40016462-CH5-SW1

Basically you reboot your mac holding CMD+R, when it boots into recovery mode, open a terminal (utils menu) and type "csrutil disable". Reboot out of that and I can now load the driver at least:

Code: [Select]
MacBook-Pro:Extensions jules$ sudo kextutil -n -t /Library/Extensions/FTDIUSBSerialDriver.kext
Kext with invalid signatured (-67030) allowed: <OSKext 0x7fea0fd3a800 [0x7fff9a0228e0]> { URL = "file:///Library/Extensions/FTDIUSBSerialDriver.kext/", ID = "com.FTDI.driver.FTDIUSBSerialDriver" }
Code Signing Failure: code signature is invalid
Warnings:
    Dependency lacks appropriate value for OSBundleRequired and may not be available during early boot:
        com.apple.iokit.IOSerialFamily - Safe Boot

Warnings:
    Dependency lacks appropriate value for OSBundleRequired and may not be available during early boot:
        com.apple.iokit.IOSerialFamily - Safe Boot

/Library/Extensions/FTDIUSBSerialDriver.kext appears to be loadable (including linkage for on-disk libraries).
MacBook-Pro:Extensions jules$ sudo kextload -b com.FTDI.driver.FTDIUSBSerialDriver

That didn't quite get me to OpenOCD attaching, but the driver shows up, at least, and I see /dev/tty.usbserial-OL0BBD9DB
27
JTAG / Re: ARM-USB-OCD-H Mac FTDI drivers
« Last post by julesb on December 01, 2018, 05:11:17 AM »
I'm having the exact same problem on 10.14 OS X Mojave, and I agree that it seems to be the edit of the product ID in /System/Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist which is rendering the driver signature invalid:

Code: [Select]
MacBook-Pro:Extensions jules$ sudo kextutil -n -t /Library/Extensions/FTDIUSBSerialDriver.kext
Warnings:
    Dependency lacks appropriate value for OSBundleRequired and may not be available during early boot:
        com.apple.iokit.IOSerialFamily - Safe Boot

/Library/Extensions/FTDIUSBSerialDriver.kext appears to be loadable (including linkage for on-disk libraries).

# Update the PID:
MacBook-Pro:Extensions jules$ sudo emacs /Library/Extensions/FTDIUSBSerialDriver.kext/Contents/Info.plist

# Re-check driver
MacBook-Pro:Extensions jules$ sudo kextutil -n -t /Library/Extensions/FTDIUSBSerialDriver.kext
Basic validation of bundle failed (-67030): /Library/Extensions/FTDIUSBSerialDriver.kext
Untrusted kexts are not allowed
Kext with invalid signature (-67030) denied: /Library/StagedExtensions/Library/Extensions/456B8BF0-702F-4694-9E5A-D9A1A80C38A7.kext
Bundle (/Library/Extensions/FTDIUSBSerialDriver.kext) failed to validate, deleting: /Library/StagedExtensions/Library/Extensions/456B8BF0-702F-4694-9E5A-D9A1A80C38A7.kext
Unable to stage kext (/Library/Extensions/FTDIUSBSerialDriver.kext) to secure location.

Is there really no work-around for this?

From some googling, It's not obvious that driver signing can be disabled on a per-driver basis somehow.

Anyone have any ideas?

28
JTAG / Re: ARM-USB-OCD-H Mac FTDI drivers
« Last post by LubOlimex on November 30, 2018, 03:54:10 PM »
I don't think FTDI would do that but it is worth the try.

We haven't even tested these instructions ourselves, a customer provided us with the instructions in the manual; we have no experience with Mac OS ourselves.
29
JTAG / Re: ARM-USB-OCD-H Mac FTDI drivers
« Last post by wiltshiretom on November 30, 2018, 03:26:29 PM »
Hi, Thanks for the response.
I think the problem arises because the Olimex instructions recommend editing the Info.plist file to change the idProduct field to match the ARM-USB-OCD-H PID. Modifying the Info.plist file breaks the kext signing and even with SIP disabled the driver does not load because the signing is invalided by the plist change. Without modifying the plist though the JTAG programmer is not mapped to the correct kext so I'm a bit stuck!

FTDI responded to my support request and explained the above which sounds like a good diagnosis of the problem.

Should we request FTDI to add PID=43/VID=5562 for the ARM-USB-OCD-H? Other Mac users must also have this problem in the field.

Any other suggested workarounds?
30
A20 / Re: fsck error
« Last post by nirp on November 30, 2018, 02:31:25 PM »
"Can you run fsck again on the NAND flash storage device after booting with a micro SD and post the output?"

If I do as u told me it'll definitely not giving any error.

thank you so much for your advice JC and JohnS.
Pages: 1 2 [3] 4 5 ... 10